fix structure of the document

Author: salonichf5

Diff for: site/content/how-to/monitoring/troubleshooting.md

@@ -14,7 +14,7 @@ This topic describes possible issues users might encounter when using NGINX Gate
 
 When investigating a problem or requesting help, there are important data points that can be collected to help understand what issues may exist.
 
-##### Resource status
+#### Resource status
 
 To check the status of a resource, use `kubectl describe`. This example checks the status of the `coffee` HTTPRoute, which has an error:
 
@@ -52,7 +52,7 @@ If a resource has errors relating to its configuration or relationship to other
 
 If no `Status` is written on the resource, further debug by checking if the referenced resources exists and belong to NGINX Gateway Fabric.
 
-##### Events
+#### Events
 
 Events created by NGINX Gateway Fabric or other Kubernetes components could indicate system or configuration issues. To see events:
 
@@ -68,15 +68,15 @@ LAST SEEN   TYPE      REASON              OBJECT
 5s          Warning   ResourceDeleted     nginxgateway/ngf-config                          NginxGateway configuration was deleted; using defaults
 ```
 
-##### Get shell access to NGINX container
+#### Get shell access to NGINX container
 
 Getting shell access to containers allows developers and operators to view the environment of a running container, see its logs or diagnose any problems. To get shell access to the NGINX container, use `kubectl exec`:
 
 ```shell
 kubectl exec -it -n nginx-gateway  <ngf-pod-name> -c nginx /bin/sh
 ```
 
-##### Logs
+#### Logs
 
 Logs from the NGINX Gateway Fabric control plane and data plane can contain information that isn't available to status or events. These can include errors in processing or passing traffic.
 
@@ -136,7 +136,7 @@ You can see logs for a crashed or killed container by adding the `-p` flag to th
 
 To see debug logs for control plane in NGINX Gateway Fabric, enable verbose logging by editing the `NginxGateway` configuration. This can be done either before or after deploying NGINX Gateway Fabric. Refer to this [guide](https://docs.nginx.com/nginx-gateway-fabric/how-to/configuration/control-plane-configuration) to do so.
 
-### Understanding the generated NGINX config
+#### Understanding the generated NGINX config
 
 Understanding the NGINX configuration is key for fixing issues because it shows how NGINX handles requests. This helps tweak settings to make sure NGINX behaves the way you want it to for your application. To see your current configuration, you can open a shell in the _nginx_ container by following these [steps](#get-shell-access-to-nginx-container) and run `nginx -T`. To understand the usage of NGINX directives in the configuration file, consult this list of [NGINX directives](https://nginx.org/en/docs/dirindex.html).