updating content files

content/github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md

@@ -24,7 +24,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 
 For more details, see <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>this issue report</a>.
 
-### Resolution
+## Resolution
 
 You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`:
 

content/github/authenticating-to-github/troubleshooting-ssh/error-bad-file-number.md

@@ -22,9 +22,9 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 > ssh: connect to host {% data variables.command_line.codeblock %} port 22: Bad file number
 ```
 
-### Solving the issue
+## Solving the issue
 
-#### Use HTTPS
+### Use HTTPS
 
 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](/github/getting-started-with-github/about-remote-repositories) you're using:
 
@@ -37,13 +37,13 @@ $ git clone https://{% data variables.command_line.codeblock %}/<em>username</em
 > Unpacking objects: 100% (84/84), done.
 ```
 
-#### Test from a different network
+### Test from a different network
 
 If you can connect the computer to another network that doesn't have a firewall, you can try testing your SSH connection to {% data variables.product.product_name %}. If everything works as it should, contact your network administrator for help on changing the firewall settings to allow your SSH connection to {% data variables.product.product_name %} to succeed.
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-#### Using SSH over the HTTPS port
+### Using SSH over the HTTPS port
 
 If using HTTPS is not an option, and your firewall admin refuses to allow SSH connections, you can try using [SSH over the HTTPS port](/articles/using-ssh-over-the-https-port) instead.
 
@@ -51,7 +51,7 @@ If using HTTPS is not an option, and your firewall admin refuses to allow SSH co
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-### Further reading
+## Further reading
 
 - "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
 

content/github/authenticating-to-github/troubleshooting-ssh/error-key-already-in-use.md

@@ -11,7 +11,7 @@ versions:
 topics:
   - SSH
 ---
-### Finding where the key has been used
+## Finding where the key has been used
 
 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:
 
@@ -24,12 +24,12 @@ $ ssh -T -ai <em>~/.ssh/id_rsa</em> git@{% data variables.command_line.codeblock
 
 The *username* in the response is the {% data variables.product.product_name %} account that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys).
 
-### Fixing the issue
+## Fixing the issue
 
 To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account).
 
 If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and [generate a brand new one](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
 
-### Deploy keys
+## Deploy keys
 
 Once a key has been attached to one repository as a deploy key, it cannot be used on another repository.  If you're running into this error while setting up deploy keys, see "[Managing deploy keys](/guides/managing-deploy-keys)."

content/github/authenticating-to-github/troubleshooting-ssh/error-permission-denied-publickey.md

@@ -11,11 +11,11 @@ versions:
 topics:
   - SSH
 ---
-### Should the `sudo` command be used with Git?
+## Should the `sudo` command be used with Git?
 
 You should not be using the `sudo` command with Git. If you have a *very good reason* you must use `sudo`, then ensure you are using it with every command (it's probably just better to use `su` to get a shell as root at that point). If you [generate SSH keys](/articles/generating-an-ssh-key) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated.
 
-### Check that you are connecting to the correct server
+## Check that you are connecting to the correct server
 
 Typing is hard, we all know it. Pay attention to what you type; you won't be able to connect to "githib.com" or "guthub.com". In some cases, a corporate network may cause issues resolving the DNS record as well.
 
@@ -32,7 +32,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 
 The connection should be made on port 22{% if currentVersion == "free-pro-team@latest" %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}.
 
-### Always use the "git" user
+## Always use the "git" user
 
 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:
 
@@ -49,7 +49,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > Hi <em>username</em>! You've successfully authenticated...
 ```
 
-### Make sure you have a key that is being used
+## Make sure you have a key that is being used
 
 {% mac %}
 
@@ -145,7 +145,7 @@ The `ssh-add` command *should* print out a long string of numbers and letters. I
 
 {% endtip %}
 
-#### Getting more details
+### Getting more details
 
 You can also check that the key is being used by trying to connect to `git@{% data variables.command_line.backticks %}`:
 
@@ -177,7 +177,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 > debug1: Offering RSA public key: /Users/<em>you</em>/.ssh/id_rsa
 ```
 
-### Verify the public key is attached to your account
+## Verify the public key is attached to your account
 
 You must provide your public key to {% data variables.product.product_name %} to establish a secure connection.
 

content/github/authenticating-to-github/troubleshooting-ssh/error-ssh-add-illegal-option----k.md

@@ -14,7 +14,7 @@ topics:
 ---
 The `-K` option is in Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an ssh key to the ssh-agent. If you have installed a different version of `ssh-add`, it may lack support for `-K`.
 
-### Solving the issue
+## Solving the issue
 
 To add your SSH private key to the ssh-agent, you can specify the path to the Apple version of `ssh-add`:
 
@@ -28,7 +28,7 @@ To add your SSH private key to the ssh-agent, you can specify the path to the Ap
 
 {% endnote %}
 
-### Further reading
+## Further reading
 
 - "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"
 - [Linux man page for SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html)

content/github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type.md

@@ -10,15 +10,15 @@ topics:
 redirect_from:
   - /github/authenticating-to-github/error-unknown-key-type
 ---
-### About the `unknown key type` error
+## About the `unknown key type` error
 
 When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
 
-### Prerequisites
+## Prerequisites
 
 You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
 
-### Solving the issue
+## Solving the issue
 
 {% warning %}
 

content/github/authenticating-to-github/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md

@@ -22,6 +22,6 @@ to approve this key so we know it's safe.
 Fingerprint: ab:08:46:83:ff:f6:c4:f8:a9:4e:68:6b:94:17:f2:46
 fatal: could not read from remote repository
 ```
-### Solving the issue
+## Solving the issue
 
 To fix this, you need to [review your SSH keys](/articles/reviewing-your-ssh-keys) and either reject or approve the unverified key. Clicking the URL link in the error message brings you to the SSH Settings page, where the unverified SSH key is highlighted in the SSH key list.

content/github/authenticating-to-github/troubleshooting-ssh/using-ssh-over-the-https-port.md

@@ -25,7 +25,7 @@ $ ssh -T -p 443 git@ssh.github.com
 
 If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
 
-### Enabling SSH connections over HTTPS
+## Enabling SSH connections over HTTPS
 
 If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.product.product_location %} to run though that server and port.