Conversation
The 2FA pages described the recovery code as a reusable backup and left out the lost-device sign-in path, the verified-email and enforced-SSO conditions, and the exact control names on the settings screens. Add a callout that the recovery code works once and turns 2FA off, add the "Sign in with your recovery code" steps, name the Copy, Download, Print, QR Code, and Text Code controls, scope the authenticator prompt to password sign-in, shorten the benefits list, and add next steps. Co-authored-by: Cursor <cursoragent@cursor.com>
The refreshed 2FA pages still used label-and-colon bullets, negative contractions, generic titles and keywords, and inline links that pushed lines past 80 characters. Remove the Key benefits list, rewrite negative contractions, match the avatar navigation wording used elsewhere, sharpen the page titles, descriptions, and keywords for search, rename the Support section, and move long links to reference definitions. Co-authored-by: Cursor <cursoragent@cursor.com>
The 2FA section page was a procedure: after two sentences it went into prerequisites, enable steps, and disable steps, and it left out how the second factor is asked for, when the CLI needs a personal access token, and what the recovery code does. Move the prerequisites, enable, and disable steps to a new manage.md and add a section for moving 2FA to a new device. Rewrite _index.md as an overview that explains the TOTP pairing and sign-in prompt, lists when Docker asks for the code, and describes the single-use recovery code and the emails Docker sends. Move the disable-2fa aliases to manage.md and point the "enable" links from the accounts pages and the recovery page at the new manage page. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep how 2FA works, when Docker asks for the code, and recovery-code behavior on the overview so the manage and recover pages stay procedural. Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
aevesdocker
reviewed
Oct 1, 2026
aevesdocker
reviewed
Oct 1, 2026
aevesdocker
approved these changes
Oct 1, 2026
aevesdocker
left a comment
aevesdocker
left a comment
Contributor
There was a problem hiding this comment.
nice changes, added two non-blocking questions
The sign-in table on the 2FA overview had a row for enforced SSO, which does not apply to the individual accounts this page covers. The manage page opened with a sentence about setup being unavailable while 2FA is on, which repeated the Move 2FA to a new device section. Co-authored-by: Cursor <cursoragent@cursor.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 2FA section page mixed concepts with enable and disable steps, and the same recovery-code and sign-in details appeared on more than one page. This splits procedures onto a manage page, keeps the overview to how 2FA works and when Docker asks for the code, and leaves the recover page for the recovery-code and Support steps.