Minor fixes to troubleshooting guides titles

Katie Horne · Katie Horne · commit ff6e799c8ed5 · 2021-08-06T11:27:59.000-05:00
diff --git a/guides/troubleshooting/docker-problems.md b/guides/troubleshooting/docker-problems.md
@@ -1,5 +1,5 @@
 ---
-title: Docker troubleshooting
+title: Docker
 description: Learn how to solve Docker issues inside Coder workspaces.
 ---
 
@@ -21,7 +21,7 @@ and size of keys each user can have.
 ## Resolution
 
 To fix this error, you can increase `maxkeys` and `maxbytes`. These are global
-settings that apply to *all* users sharing the same system. You can modify this
+settings that apply to _all_ users sharing the same system. You can modify this
 by adding the following to the `sysctl` configuration file:
 
 ```console
diff --git a/guides/troubleshooting/registry.md b/guides/troubleshooting/registry.md
@@ -1,5 +1,5 @@
 ---
-title: Image registry troubleshooting
+title: Image registry
 description: Learn how to resolve issues connecting to an image registry.
 ---
 
@@ -18,8 +18,7 @@ certificate signed by unknown authority
 The local registry you are configuring is expecting a valid certificate to
 authenticate the connection with Coder. You will receive this error if:
 
-- You do not have a certificate
-configured
+- You do not have a certificate configured
 - There is an issue with the certificate itself
 
 > Coder uses Docker's Registry 2.0 implementation, which supports self-signed
@@ -28,8 +27,9 @@ configured
 ## Troubleshooting steps
 
 - If you haven't created the local registry, and you haven't generated the
-  self-signed certificate, [please see our
-  documentation](../../setup/air-gapped/infrastructure.md) on setting these up.
+  self-signed certificate,
+  [please see our documentation](../../setup/air-gapped/infrastructure.md) on
+  setting these up.
 
 - Check to see if your `registry.crt` file is stored in the correct location on
   each of your Kubernetes nodes. Depending upon your Linux distribution and
@@ -53,9 +53,9 @@ configured
 Ensure that you've created the self-signed certificate secret in your Kubernetes
 cluster:
 
-  ```console
-  kubectl -n coder get secret local-registry-cert -o yaml
-  ```
+```console
+kubectl -n coder get secret local-registry-cert -o yaml
+```
 
-If none of these steps resolve the issue, please [contact
-us](https://coder.com/contact) for further support.
+If none of these steps resolve the issue, please
+[contact us](https://coder.com/contact) for further support.
