updating content files

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)"