Apply style guide to some "YOUR_*" placeholders

[hsnabszhdn]

Why:

The style guide on placeholders is to separate words with -, not _:

If a placeholder is multiple words, connect the words with dashes (kebab-case)

style-guide#placeholders

Closes: N/A

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

There is a lot more in the repository, but these three are what I can comfortably change/test in a single PR:

• YOUR_USERNAME -> YOUR-USERNAME
• YOUR_REPOSITORY -> YOUR-REPOSITORY
• YOUR_FORK -> YOUR-FORK

Also, changed a single occurrence of your_listed_directory and YOUR_PERSONAL_ACCESS_TOKEN to be consistent in the pages changed by the above global replacement.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• 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
account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9
authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9
communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9
contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9
pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9
pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.12 3.11 3.10 3.9

---

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

[nguyenalex836]

@itecompro Thanks so much for opening a PR with these fixes! I'll update the branch and get this merged once tests are passing 🍏

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