Changes lt/gt HTML tags to angle brackets in plaintext (#39458)

Author: subatoi

Diff for: content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md

@@ -53,12 +53,12 @@ You can display the command-line help for any command using the <nobr>`--help`</
 
    ```shell
    # Single supported language - create one CodeQL database
-   codeql database create &lt;database&gt; --command &lt;build&gt; \
-         --language=&lt;language-identifier&gt;
+   codeql database create <database> --command <build> \
+         --language=<language-identifier>
 
    # Multiple supported languages - create one CodeQL database per language
-   codeql database create &lt;database&gt; --command &lt;build&gt; \
-         --db-cluster --language=&lt;language-identifier&gt;,&lt;language-identifier&gt;
+   codeql database create <database> --command <build> \
+         --db-cluster --language=<language-identifier>,<language-identifier>
    ```
 
    {% note %}
@@ -134,18 +134,18 @@ $
 1. Run `codeql database analyze` on the database and specify which {% ifversion codeql-packs %}packs and/or {% endif %}queries to use.
 
    ```shell
-   codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
-       --output=&lt;output&gt;  {% ifversion codeql-packs %}--download &lt;packs,queries&gt;{% else %}&lt;queries&gt;{% endif %}
+   codeql database analyze <database> --format=<format> \
+       --output=<output>  {% ifversion codeql-packs %}--download <packs,queries>{% else %}<queries>{% endif %}
    ```
 
 {% note %}
 
 **Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
 
 ```shell
-codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
-    --sarif-category=&lt;language-specifier&gt; --output=&lt;output&gt; \
-    {% ifversion codeql-packs %}&lt;packs,queries&gt;{% else %}&lt;queries&gt;{% endif %}
+codeql database analyze <database> --format=<format> \
+    --sarif-category=<language-specifier> --output=<output> \
+    {% ifversion codeql-packs %}<packs,queries>{% else %}<queries>{% endif %}
 ```
 
 {% endnote %}
@@ -213,17 +213,17 @@ When you have decided on the most secure and reliable method for your CI server,
 
 ```shell
 # {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} available from a secret store
-&lt;call-to-retrieve-secret&gt; | codeql github upload-results \
-    --repository=&lt;repository-name&gt; \
-    --ref=&lt;ref&gt; --commit=&lt;commit&gt; \
-    --sarif=&lt;file&gt; {% ifversion ghes or ghae %}--github-url=&lt;URL&gt; \
+<call-to-retrieve-secret> | codeql github upload-results \
+    --repository=<repository-name> \
+    --ref=<ref> --commit=<commit> \
+    --sarif=<file> {% ifversion ghes or ghae %}--github-url=<URL> \
     {% endif %}--github-auth-stdin
 
 # {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} available in GITHUB_TOKEN
 codeql github upload-results \
-    --repository=&lt;repository-name&gt; \
-    --ref=&lt;ref&gt; --commit=&lt;commit&gt; \
-    --sarif=&lt;file&gt; {% ifversion ghes or ghae %}--github-url=&lt;URL&gt; \
+    --repository=<repository-name> \
+    --ref=<ref> --commit=<commit> \
+    --sarif=<file> {% ifversion ghes or ghae %}--github-url=<URL> \
     {% endif %}
 ```
 
@@ -349,7 +349,7 @@ $ echo $OCTO-ORG_ACCESS_TOKEN | codeql database analyze --download /codeql-dbs/e
 If you want to download a {% data variables.product.prodname_codeql %} pack without running it immediately, then you can use the `codeql pack download` command. This is useful if you want to avoid accessing the internet when running {% data variables.product.prodname_codeql %} queries. When you run the {% data variables.product.prodname_codeql %} analysis, you can specify packs, versions, and paths in the same way as in the previous example:
 
 ```shell
-echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download &lt;scope/name@version:path&gt; &lt;scope/name@version:path&gt; ...
+echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download <scope/name@version:path> <scope/name@version:path> ...
 ```
 
 ### Downloading {% data variables.product.prodname_codeql %} packs from multiple {% data variables.product.company_short %} container registries

Diff for: content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md

@@ -78,9 +78,9 @@ codeql database analyze <database> --format=<format> --output=<output> <query-sp
 **Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
 
 ```shell
-codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
-    --sarif-category=&lt;language-specifier&gt; --output=&lt;output&gt; \
-    {% ifversion codeql-packs %}&lt;packs,queries&gt;{% else %}&lt;queries&gt;{% endif %}
+codeql database analyze <database> --format=<format> \
+    --sarif-category=<language-specifier> --output=<output> \
+    {% ifversion codeql-packs %}<packs,queries>{% else %}<queries>{% endif %}
 ```
 {% endnote %}
 

Diff for: content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md

@@ -103,7 +103,7 @@ $ echo $OCTO-ORG_ACCESS_TOKEN | codeql database analyze --download /codeql-dbs/e
 If you want to download a {% data variables.product.prodname_codeql %} pack without running it immediately, then you can use the `codeql pack download` command. This is useful if you want to avoid accessing the internet when running {% data variables.product.prodname_codeql %} queries. When you run the {% data variables.product.prodname_codeql %} analysis, you can specify packs, versions, and paths in the same way as in the previous example:
 
 ```shell
-echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download <scope/name@version:path> <scope/name@version:path> ...
+echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download <scope/name@version:path> <scope/name@version:path> ...
 ```
 
 ### Downloading {% data variables.product.prodname_codeql %} packs from multiple {% data variables.product.company_short %} container registries

Diff for: content/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github.md

@@ -36,17 +36,17 @@ When you have decided on the most secure and reliable method for your configurat
 
 ```shell
 # {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} available from a secret store
-<call-to-retrieve-secret> | codeql github upload-results \
-    --repository=<repository-name> \
-    --ref=<ref> --commit=<commit> \
-    --sarif=<file> {% ifversion ghes or ghae %}--github-url=<URL> \
+<call-to-retrieve-secret> | codeql github upload-results \
+    --repository=<repository-name> \
+    --ref=<ref> --commit=<commit> \
+    --sarif=<file> {% ifversion ghes or ghae %}--github-url=<URL> \
     {% endif %}--github-auth-stdin
 
 # {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} available in GITHUB_TOKEN
 codeql github upload-results \
-    --repository=&lt;repository-name&gt; \
-    --ref=&lt;ref&gt; --commit=&lt;commit&gt; \
-    --sarif=&lt;file&gt; {% ifversion ghes or ghae %}--github-url=&lt;URL&gt; \
+    --repository=<repository-name> \
+    --ref=<ref> --commit=<commit> \
+    --sarif=<file> {% ifversion ghes or ghae %}--github-url=<URL> \
     {% endif %}
 ```
 

Diff for: content/get-started/getting-started-with-git/about-remote-repositories.md

@@ -34,7 +34,7 @@ You can use the `git remote add` command to match a remote URL with a name.
 For example, you'd type the following in the command line:
 
 ```shell
-git remote add origin <REMOTE_URL>
+git remote add origin <REMOTE_URL>
 ```
 
 This associates the name `origin` with the `REMOTE_URL`.

Diff for: content/migrations/importing-source-code/using-the-command-line-to-import-source-code/adding-locally-hosted-code-to-github.md

@@ -98,7 +98,7 @@ After you've initialized a Git repository, you can push the repository to {% dat
 1. [Add the URL for the remote repository](/get-started/getting-started-with-git/managing-remote-repositories) where your local repository will be pushed.
 
    ```shell
-   $ git remote add origin <REMOTE_URL>
+   $ git remote add origin <REMOTE_URL>
    # Sets the new remote
    $ git remote -v
    # Verifies the new remote URL
@@ -124,7 +124,7 @@ After you've initialized a Git repository, you can push the repository to {% dat
 1. In the Command prompt, [add the URL for the remote repository](/get-started/getting-started-with-git/managing-remote-repositories) where your local repository will be pushed.
 
    ```shell
-   $ git remote add origin &lt;REMOTE_URL>
+   $ git remote add origin <REMOTE_URL>
    # Sets the new remote
    $ git remote -v
    # Verifies the new remote URL
@@ -150,7 +150,7 @@ After you've initialized a Git repository, you can push the repository to {% dat
 1. [Add the URL for the remote repository](/get-started/getting-started-with-git/managing-remote-repositories) where your local repository will be pushed.
 
    ```shell
-   $ git remote add origin &lt;REMOTE_URL>
+   $ git remote add origin <REMOTE_URL>
    # Sets the new remote
    $ git remote -v
    # Verifies the new remote URL

Diff for: content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md

@@ -118,7 +118,7 @@ publishing {
         }
     }
     publications {
-        register<MavenPublication>("gpr") {
+        register<MavenPublication>("gpr") {
             from(components["java"])
         }
     }
@@ -133,7 +133,7 @@ plugins {
 }
 subprojects {
     apply(plugin = "maven-publish")
-    configure&lt;PublishingExtension> {
+    configure<PublishingExtension> {
         repositories {
             maven {
                 name = "GitHubPackages"
@@ -145,7 +145,7 @@ subprojects {
             }
         }
         publications {
-            register&lt;MavenPublication>("gpr") {
+            register<MavenPublication>("gpr") {
                 from(components["java"])
             }
         }