[Improvement]: Use consistent styling for placeholder and variable text

[docs-bot]

[maintainer edit] This issue is reserved for the MLH Fellowship program.

Is this issue for a product update or release that is not yet available to customers?

No? Then please continue. Thank you!

What article(s) is affected?

Probably a lot, but my regex knowledge limited me from figuring out exactly how many articles. Need to find instances of <string> that aren't tags for list items, code, or URLs.

Describe the desired docs changes and the problem they solve for customers.

Right now, our docs use a variety of styles for placeholder and variable text. We should be using all uppercase, but there are instances of <strings> and other non-uppercase styling. Similar to how we removed <em> tags from code examples (https://github.com/github/docs/issues/20890), this might be a good issue for OS contributors.

Who does this affect?

People using the docs who might not recognize placeholder or variable text. Contributors trying to learn GitHub Docs style

What is the impact to users?

Possible confusion over what text is a placeholder or variable.

Are you willing to open a PR to make this fix? If not, do you know anyone (Hubber or not, we're open source!) who's willing to help write this documentation?

I recommend this going to our OS community :sparkle:

[SwanseN21]

Let's work together

[Said182]

Let's work together

[cmwilson21]

This issue is reserved for the MLH Fellowship program.

[github-actions[bot]]

A stale label has been added to this issue becuase it has been open for 60 days with no activity. To keep this issue open, add a comment within 3 days.

[cmwilson21]

Reopening as stalebot closed it a bit early 😄