[docs-scanner] 2FA account recovery instructions contain logical contradiction

content/manuals/security/authentication/2fa/recover-hub-account.md を開き、現在の "Recover your account without access" セクションを確認します。Docker の実際のサインインおよび 2FA 回復フローを検証し、紛失したデバイスのオプションが認証の前と後のどちらに表示されるか、また Contact Support フォームが必須かどうかを確認します。手順がユーザーエクスペリエンスと一致し、矛盾する手順を提示していなければ完了です。

File: content/manuals/security/authentication/2fa/recover-hub-account.md

Issue

The "Recover your account without access" section instructs users to sign in with username and password when they've lost both their 2FA device and recovery code:

If you lost access to both your two-factor authentication application and your recovery code:

1. Sign in to your Docker account with your username and password.
2. Select I've lost my authentication device and I've lost my recovery code.

Why this matters

This is a logical contradiction that will confuse users in a critical account recovery situation. When 2FA is enabled on an account, signing in requires:

1. Username and password
2. The 2FA code from the authenticator app

If a user has lost their authentication device, they cannot provide the 2FA code, which means they cannot complete step 1 (signing in). The instructions don't explain how to bypass the 2FA prompt or access the "I've lost my authentication device" option without being able to sign in first.

A user following these instructions will be stuck at the sign-in page, unable to proceed to step 2 where they can indicate they've lost their device.

Suggested fix

Clarify the actual recovery flow. Possible approaches:

1. If there's a "lost device" link on the sign-in page itself (before completing authentication), explain that:

   • Go to the sign-in page
   • Enter username and password
   • When prompted for 2FA code, select "I've lost my authentication device"
   • Then select "I've lost my recovery code"

2. If users must contact support without being able to sign in at all, simplify to:

   • If you've lost both your authentication device and recovery code, you cannot sign in
   • Complete the Contact Support form with your primary email address for recovery instructions

The instructions should match the actual user experience when 2FA blocks sign-in.

Found by nightly documentation quality scanner