Fix incorrect indentation in managing-a-custom-domain-for-your-github-pages-site.md

[Marcono1234]

Why:

Closes #22180

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

Fixes incorrect indentation of the note. Previously it was not indented and would cause the list to be split, with the next item starting at "1." again, see also description of #22180.

Check off the following:

• I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
• For content changes, I have completed the self-review checklist.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md	fpt ghec	fpt ghec

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

[Marcono1234]

Now the list numbering seems to be correct, but Markdown rendering is broken for this note:

Maybe this is also only an intermittent issue like the broken rendering in #22180, though that is really weird then. I am seeing this in Firefox and Edge, both in private windows, so I don't think this is caused by the browser cache (?).

[cmwilson21]

@Marcono1234 Thanks for opening a PR! I'll get this triaged for review ⚡

As for the markdown in the note, I followed your advice with Firefox and a private browser and have been unable to recreate it. Perhaps you are right and it was a temp bug or it may have been fixed in an internal PR. Either way, thanks for the heads up about it! ✨

[vgrl]

Thanks, @Marcono1234 ⚡ I'm going to make a small edit, and then I'll merge this.

[vgrl]

Looks good on preview now. 🎉

I'll go ahead and get this PR merged, thanks again @Marcono1234 !

[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 ⚡