From 9b1367444098af608ff48c128fba1f3cd94555c1 Mon Sep 17 00:00:00 2001 From: disqualifier Date: Mon, 6 Jul 2026 00:12:11 -0400 Subject: [PATCH] docs: fix broken antecedent and de-duplicate the cache-button omit note The omit-cache sentence was spliced mid-paragraph between the raw-id problem statement and "The cache button fixes that", so "that" resolved to the wrong antecedent (the omit-cache mechanics instead of the raw-id rendering problem). The same note already exists standalone later in the section, so the spliced copy was also a duplicate. Drop it from the lead paragraph and keep the one standalone copy. Signed-off-by: disqualifier --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 4fe2d37..768780b 100644 --- a/README.md +++ b/README.md @@ -115,8 +115,6 @@ echoes its `data`. ## Cache button (mention priming) Discord clients render `<@id>` as a raw id until the user object is cached locally. -Omit `cache` (or pass `None` / `[]`) and the button never appears; a non-empty cache -must have one entry per page or construction raises. The cache button fixes that: pass `cache=[...]` with one entry per page, where each entry is a string of the user mentions on that page (`"<@111> <@222> <@333>"`).