Queue & reviews

When a release or code change looks like it affects something a mapped page says, Amendary drafts a correction: the sentence that is now wrong, the proposed replacement, and the evidence behind it. By default a confident correction with complete context is applied to the page automatically. In review mode (Settings) every one waits for you first.

It is how sure Amendary is that the page actually needs updating. Corrections are only drafted above a certain confidence, so you will not see a flood of maybes. By the time one reaches you, it is worth a look.

Whatever needs a person: a page or change too large to read fully (“Partial context”), or a case where Amendary could not draft a confident edit. In review mode, every correction lands there instead. The Resolved tab lists what was applied or dismissed, with Undo next to each applied one.

Amendary replaces the affected sentence with the correction, or with your edited version if you changed it first. When it cannot place the edit exactly, it posts a comment on the page instead of guessing. Every applied change is in the Activity log with the release or diff that caused it and the text it replaced.

Open the Resolved tab of the Queue and select Undo next to the correction. Amendary checks that the block has not been edited since, then restores the stored original text. Undo is available for 30 days after a correction is applied and works the same on every Notion plan. Notion’s own page history is an extra safety net, but its retention depends on your Notion plan and it only exists inside the Notion UI, so Amendary does not rely on it.

Undo it, or if you have already fixed the page by hand, use Mark wrong next to Undo and say briefly why. Marking a correction wrong does not touch the page; it records the miss so the same kind of correction is held for review next time.

It is marked as not relevant and cleared from the Queue. There is no penalty for dismissing: if the correction did not apply, dismissing it is exactly the right move. You can say why (wrong page, wrong correction, not actually stale); the reason is recorded so you can track accuracy over time.

Yes, snooze it. A snoozed correction leaves the Queue and comes back after the snooze period (7 days by default). The Snoozed tab shows everything you have set aside and when each one returns.

Three places: your repos’ published GitHub Releases (for pages tagged “Help center”), the daily check of code changes (for pages tagged “Engineering docs”), and a one-time audit that runs right after you map a page. Each correction shows where it came from.

A few common reasons: the page is not mapped to the repo that changed, the page is tagged “Excluded”, or the change did not clear the confidence bar Amendary uses to avoid noisy, low-value edits. See Troubleshooting if something still seems off.