@@ -130,7 +130,7 @@ Email notifications from {% data variables.product.prodname_dotcom %} contain he
 | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
 | `To` field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. |
 | `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% ifversion fpt or ghec %}`@noreply.github.com`{% else %}based on the no-reply email address configured by your site administrator{% endif %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li><li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li><li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
-| `List-Id` field | This field identifies the name of the repository and its owner. The format of this address is always `OWNER/REPOSITORY <REPOSITORY.OWNER>`, e.g. `List-Id: grain-lang/grain <grain.grain-lang.{% data variables.command_line.backticks %}>`. |
+| `List-Id` field | This field identifies the name of the repository and its owner. The format of this address is always `OWNER/REPOSITORY <REPOSITORY.OWNER>`, e.g. `List-Id: grain-lang/grain <grain.grain-lang.{% data variables.product.product_url %}>`. |
 | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." |
 
 ## Choosing your notification settings
 
@@ -63,11 +63,11 @@ If you have any local copies of personal repositories you have created or forked
 $ cd YOUR-REPOSITORY
 # Change directories to the initialized Git repository
 $ git remote -v
-origin	https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git (fetch)
-origin	https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git (push)
+origin	https://{% data variables.product.product_url %}/YOUR-USERNAME/YOUR-REPOSITORY.git (fetch)
+origin	https://{% data variables.product.product_url %}/YOUR-USERNAME/YOUR-REPOSITORY.git (push)
 ```
 
-Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+Your user name is what immediately follows the `https://{% data variables.product.product_url %}/`.
 
 {% ifversion fpt or ghec %}
 
 
@@ -76,7 +76,7 @@ If the new owner of your old username creates a repository with the same name as
 
 ## Links to your previous profile page
 
-After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+After changing your username, links to your previous profile page, such as `https://{% data variables.product.product_url %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
 
 ## Your Git commits
 
 
@@ -25,14 +25,14 @@ You'll need to authenticate this action using your password, which is the SSH ke
 1. Enter the following:
 
    ```shell replacedomain copy
-   ssh -T git@{% data variables.command_line.codeblock %}
+   ssh -T git@{% data variables.product.product_url %}
    # Attempts to ssh to {% data variables.product.product_name %}
    ```
 
    You may see a warning like this:
 
    ```shell replacedomain
-   > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established.
+   > The authenticity of host '{% data variables.product.product_url %} (IP ADDRESS)' can't be established.
    > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
    > Are you sure you want to continue connecting (yes/no)?
    ```
 
@@ -166,7 +166,7 @@ Once you have a {% data variables.product.pat_generic %}, you can enter it inste
 For example, to clone a repository on the command line you would enter the following `git clone` command. You would then be prompted to enter your username and password. When prompted for your password, enter your {% data variables.product.pat_generic %} instead of a password.
 
 ```shell
-$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPO.git
+$ git clone https://{% data variables.product.product_url %}/USERNAME/REPO.git
 Username: YOUR-USERNAME
 Password: YOUR-PERSONAL-ACCESS-TOKEN
 ```
 
@@ -95,7 +95,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
 1. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/repositories/creating-and-managing-repositories/cloning-a-repository) to your local computer.
 
    ```shell
-   $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
+   $ git clone https://{% data variables.product.product_url %}/YOUR-USERNAME/YOUR-REPOSITORY
    > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/
    > remote: Counting objects: 1301, done.
    > remote: Compressing objects: 100% (769/769), done.
@@ -159,7 +159,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
    > Compressing objects: 100% (677/677), done.
    > Writing objects: 100% (1058/1058), 148.85 KiB, done.
    > Total 1058 (delta 590), reused 602 (delta 378)
-   > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git
+   > To https://{% data variables.product.product_url %}/YOUR-USERNAME/YOUR-REPOSITORY.git
    >  + 48dc599...051452f main -> main (forced update)
    ```
 
@@ -172,7 +172,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
    > Compressing objects: 100% (166/166), done.
    > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done.
    > Total 321 (delta 124), reused 269 (delta 108)
-   > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git
+   > To https://{% data variables.product.product_url %}/YOUR-USERNAME/YOUR-REPOSITORY.git
    >  + 48dc599...051452f main -> main (forced update)
    ```
 
 
@@ -17,7 +17,7 @@ shortTitle: Agent failure to sign
 When trying to SSH into {% data variables.location.product_location %} on a Linux computer, you may see the following message in your terminal:
 
 ```shell
-$ ssh -vT git@{% data variables.command_line.codeblock %}
+$ ssh -vT git@{% data variables.product.product_url %}
 > ...
 > Agent admitted failure to sign using the key.
 > debug1: No more authentication methods to try.
 
@@ -15,12 +15,12 @@ topics:
 When running remote Git commands or SSH, your connection might time out:
 
 ```shell
-$ ssh -vT git@{% data variables.command_line.codeblock %}
+$ ssh -vT git@{% data variables.product.product_url %}
 > OpenSSH_8.1p1, LibreSSL 2.7.3
-> debug1: Connecting to {% data variables.command_line.codeblock %} [207.97.227.239] port 22.
+> debug1: Connecting to {% data variables.product.product_url %} [207.97.227.239] port 22.
 > debug1: connect to address 207.97.227.239 port 22: Connection timed out
-> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Connection timed out
-> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Bad file number
+> ssh: connect to host {% data variables.product.product_url %} port 22: Connection timed out
+> ssh: connect to host {% data variables.product.product_url %} port 22: Bad file number
 ```
 
 ## Solving the issue
@@ -30,7 +30,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 Often, the simplest solution is to simply avoid SSH entirely. Most firewalls and proxies allow HTTPS traffic without issue. To take advantage of this, change [the remote URL](/get-started/getting-started-with-git/about-remote-repositories) you're using:
 
 ```shell
-$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPO-NAME.git
+$ git clone https://{% data variables.product.product_url %}/USERNAME/REPO-NAME.git
 > Cloning into 'reponame'...
 > remote: Counting objects: 84, done.
 > remote: Compressing objects: 100% (45/45), done.
 
@@ -17,7 +17,7 @@ topics:
 To determine where the key has already been used, open a terminal and type the `ssh` command. Use the `-i` flag to provide the path to the key you want to check:
 
 ```shell
-$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %}
+$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.product.product_url %}
 # Connect to {% data variables.location.product_location %} using a specific ssh key
 > Hi USERNAME! You've successfully authenticated, but GitHub does not
 > provide shell access.
@@ -28,7 +28,7 @@ The _username_ in the response is the account on {% data variables.location.prod
 To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option:
 
 ```shell
-ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %}
+ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.product.product_url %}
 ```
 
 ## Fixing the issue
 
@@ -25,7 +25,7 @@ If you have a _very good reason_ you must use `sudo`, then ensure you are using
 To make sure you are connecting to the right domain, you can enter the following command:
 
 ```shell replacedomain copy
-ssh -vT git@{% data variables.command_line.codeblock %}
+ssh -vT git@{% data variables.product.product_url %}
 ```
 
 You should see this output:
@@ -35,7 +35,7 @@ You should see this output:
 > debug1: Reading configuration data /Users/YOU/.ssh/config
 > debug1: Reading configuration data /etc/ssh/ssh_config
 > debug1: /etc/ssh/ssh_config line 47: Applying options for *
-> debug1: Connecting to {% data variables.command_line.codeblock %} port 22.
+> debug1: Connecting to {% data variables.product.product_url %} port 22.
 ```
 
 The connection should be made on port 22{% ifversion fpt or ghec %}, unless you're overriding settings to use [SSH over HTTPS](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port){% endif %}.
@@ -45,7 +45,7 @@ The connection should be made on port 22{% ifversion fpt or ghec %}, unless you'
 All connections, including those for remote URLs, must be made as the "git" user. If you try to connect with your {% data variables.product.product_name %} username, it will fail:
 
 ```shell replacedomain
-$ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %}
+$ ssh -T GITHUB-USERNAME@{% data variables.product.product_url %}
 > Permission denied (publickey).
 ```
 
@@ -54,7 +54,7 @@ If your connection failed and you're using a remote URL with your {% data variab
 You should verify your connection by typing:
 
 ```shell replacedomain copy
-ssh -T git@{% data variables.command_line.codeblock %}
+ssh -T git@{% data variables.product.product_url %}
 ```
 
 You should see this output:
@@ -122,10 +122,10 @@ The `ssh-add` command _should_ print out a long string of numbers and letters. I
 
 ### Getting more details
 
-You can also check that the key is being used by trying to connect to `git@{% data variables.command_line.backticks %}`:
+You can also check that the key is being used by trying to connect to `git@{% data variables.product.product_url %}`:
 
 ```shell replacedomain copy
-ssh -vT git@{% data variables.command_line.codeblock %}
+ssh -vT git@{% data variables.product.product_url %}
 ```
 
 You'll see output like this: