Repo sync

content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md

@@ -119,7 +119,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
    - Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
 
-     ```text copy
+     ```text replacedomain copy
      Host {% ifversion ghes %}HOSTNAME{% else %}github.com{% endif %}
        AddKeysToAgent yes
        UseKeychain yes
@@ -134,7 +134,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
      - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *.{% ifversion ghes %}HOSTNAME{% else %}github.com{% endif %}` section.
 
-       ```text copy
+       ```text replacedomain copy
        Host {% ifversion ghes %}HOSTNAME{% else %}github.com{% endif %}
          IgnoreUnknown UseKeychain
        ```

content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md

@@ -24,14 +24,14 @@ You'll need to authenticate this action using your password, which is the SSH ke
 {% data reusables.command_line.open_the_multi_os_terminal %}
 1. Enter the following:
 
-   ```shell copy
+   ```shell replacedomain copy
    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
+   ```shell replacedomain
    > 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)?

content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md

@@ -24,13 +24,13 @@ 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 copy
+```shell replacedomain copy
 ssh -vT git@{% data variables.product.product_url %}
 ```
 
 You should see this output:
 
-```shell
+```shell replacedomain
 > OpenSSH_8.1p1, LibreSSL 2.7.3
 > debug1: Reading configuration data /Users/YOU/.ssh/config
 > debug1: Reading configuration data /etc/ssh/ssh_config
@@ -44,7 +44,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
+```shell replacedomain
 $ ssh -T GITHUB-USERNAME@{% data variables.product.product_url %}
 > Permission denied (publickey).
 ```
@@ -53,7 +53,7 @@ If your connection failed and you're using a remote URL with your {% data variab
 
 You should verify your connection by typing:
 
-```shell copy
+```shell replacedomain copy
 ssh -T git@{% data variables.product.product_url %}
 ```
 
@@ -124,7 +124,7 @@ The `ssh-add` command _should_ print out a long string of numbers and letters. I
 
 You can also check that the key is being used by trying to connect to `git@{% data variables.product.product_url %}`:
 
-```shell copy
+```shell replacedomain copy
 ssh -vT git@{% data variables.product.product_url %}
 ```