Fixing subheading level sudo-mode.md

[ThirdEyeRose]

Was working on some docs for WordPress VIP about a similar feature and saw that one of the subheading on this page wasn't at the correct level in the hierarchy. This should fix that.

Why:

Closes: No issue - just a subheading change

What's being changed (if available, include any code snippets, screenshots, or gifs):

As you can see, the top two headings are H2s whereas the second heading should be an H3 to match the others.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment
• Message #docs-engineering on Slack for a staging server.

A Hubber will need to deploy your changes internally to review.

Table of review links

⚠️ Warning: Our review server is experiencing latency issues.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on the review server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
authentication/keeping-your-account-and-data-secure/sudo-mode.md	fpt ghec ghes@ 3.16 3.15 3.14 3.13 3.12	fpt ghec ghes@ 3.16 3.15 3.14 3.13 3.12

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[subatoi]

Hi @ThirdEyeRose, thanks for spotting and fixing that—would you be willing to change line 48, too? I don't think we need it to say "passkey key". Let me know, but either way I'm happy to merge this. Thank you!

[ThirdEyeRose]

Sure can, @subatoi ! Requested change has been made on the PR branch

[subatoi]

Awesome, thanks @ThirdEyeRose! I'll get this merged now. Thanks again for your help and interest in our docs ✨

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡