Fix vale errors in source (#24086)

* backticks for javascript

* Update sorting-search-results.md

backticks asc

* Update installing-github-enterprise-server-on-azure.md

fixed vm az

* Update searching-for-repositories.md

backticks

* Update searching-code.md

backticks

* Update searching-issues-and-pull-requests.md

backticks

* Update searching-issues-and-pull-requests.md

* Update understanding-the-search-syntax.md

* Update searching-for-packages.md

* Update upgrading-from-dependabotcom-to-github-native-dependabot.md

* fix errors in source

* removed spaces

* vale docs

* link to md link

* spacing for backticks

* docs draft

* remove space

* removed spacing

* drafting

* drafting

* draft

* escape single quote

* escape another single quote

* fix broken link

* vale guide

* edge case

* edge case ex

* edge case ex link

* grammer

* grammer

* Update vale-guide.md

clarity

* Update vale-guide.md

small edit

* clarity

* sentence fix

* Rubocop to RuboCop

* Rubocop -> RuboCop

* terms in backticks

* pem in backtick

* idp -> IdP

* file names in backticks

* public/private rsa in backticks

* fix vale errors

* fix vale errors

* Update sending-enterprise-contributions-to-your-githubcom-profile.md

fix dot-com links

* Update metadata-syntax-for-github-actions.md

* Update configuring-codeql-cli-in-your-ci-system.md

* Update content/get-started/getting-started-with-git/associating-text-editors-with-git.md

Co-authored-by: Vanessa <vgrl@github.com>

* Update managing-deploy-keys.md

public and private rsa key pair

* Update libraries.md

removed backticks for consistency

* Update sorting-search-results.md

removed backticks for consistency

* Update metadata-syntax-for-github-actions.md

removed backticks for consistency

* Update metadata-syntax-for-github-actions.md

removed backticks

* delete vale config files

Co-authored-by: Vanessa <vgrl@github.com>
Co-authored-by: Amy Burns <timeyoutakeit@github.com>

content/github/copilot/research-recitation.md

@@ -57,9 +57,9 @@ This procedure is permissive enough to let many relatively “boring” examples
 After filtering, there were 473 suggestions left. But they came in very different forms:
 
 1. Some were basically just repeats of another case that passed filtering. For example, sometimes {% data variables.product.prodname_dotcom %} Copilot makes a suggestion, the developer types a comment line, and {% data variables.product.prodname_dotcom %} Copilot offers a very similar suggestion again. I removed these cases from the analysis as duplicates.
-2. Some were long, repetitive sequences. Like the following example, where the repeated blocks of `‘<p>’` are of course found somewhere in the training set: <br>![Example repetitions](/assets/images/help/copilot/example_repetitions.png)<br> Such suggestions can be helpful (test cases, regexes) or not helpful (like this case, I suspect). But in any case, they do not fit the idea of rote learning I had in mind when I started this investigation.
+2. Some were long, repetitive sequences. Like the following example, where the repeated blocks of `‘<p>’` are of course found somewhere in the training set: <br>![Example repetitions](/assets/images/help/copilot/example_repetitions.png)<br> Such suggestions can be helpful (test cases, regular expressions) or not helpful (like this case, I suspect). But in any case, they do not fit the idea of rote learning I had in mind when I started this investigation.
 3. Some were standard inventories, like the natural numbers, or the prime numbers, or stock market tickers, or the Greek alphabet: <br>![Example of Greek alphabet](/assets/images/help/copilot/example_greek.png)
-4. Some were common, straightforward ways, perhaps even universal ways, of doing things with very few natural degrees of freedom. For example, the middle part of the following strikes me as very much the standard way of using the BeautifulSoup package to parse a wikipedia list. In fact, the best matching snippet found in {% data variables.product.prodname_dotcom %} Copilot's training data<sup id="anchor5">[5](#footnote5)</sup> uses such code to parse a different article and goes on to do different things with the results. <br>![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png) <br>This doesn’t fit my idea of a quote either. It’s a bit like when someone says “I’m taking out the trash; I’ll be back soon” -- that’s a matter of fact statement, not a quote, even though that particular phrase has been uttered many times before.
+4. Some were common, straightforward ways, perhaps even universal ways, of doing things with very few natural degrees of freedom. For example, the middle part of the following strikes me as very much the standard way of using the BeautifulSoup package to parse a Wikipedia list. In fact, the best matching snippet found in {% data variables.product.prodname_dotcom %} Copilot's training data<sup id="anchor5">[5](#footnote5)</sup> uses such code to parse a different article and goes on to do different things with the results. <br>![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png) <br>This doesn’t fit my idea of a quote either. It’s a bit like when someone says “I’m taking out the trash; I’ll be back soon” -- that’s a matter of fact statement, not a quote, even though that particular phrase has been uttered many times before.
 5. And then there are all other cases. Those with at least some specific overlap in either code or comments. These are what interests me most, and what I’m going to concentrate on from now on.
 
 This bucketing necessarily has some edge cases<sup id="anchor6">[6](#footnote6)</sup>, and your mileage may vary in how you think they should be classified. Maybe you even disagree with the whole set of buckets in the first place.