fix ordered ist

Author: salonichf5

site/content/how-to/monitoring/troubleshooting.md

@@ -80,7 +80,7 @@ kubectl exec -it -n nginx-gateway  <ngf-pod-name> -c nginx /bin/sh
 
 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.
 
-##### Container Logs
+1. Container Logs
 
 To see logs for Control plane container:
 
@@ -94,11 +94,11 @@ To see logs for Data plane container:
 kubectl -n nginx-gateway logs <ngf-pod-name> -c nginx
 ```
 
-##### Error Logs
+1. Error Logs
 
 To see error logs for control plane and data plane containers:
 
-For _nginx-gateway_ container, you can `grep` for the word `error` or change the log level to `error` by following steps in [Modify log levels](#modify-log-levels). Once you have modified log levels, you can `grep` for the word `debug` to check debug logs for further investigation.
+For _nginx-gateway_ container, you can `grep` for the word `error` or change the log level to `error` by following steps in Modify log levels (Section 3). Once you have modified log levels, you can `grep` for the word `debug` to check debug logs for further investigation.
 
 ```shell
 kubectl -n nginx-gateway logs <ngf-pod-name> -c nginx-gateway | grep error
@@ -125,14 +125,14 @@ kubectl logs -n nginx-gateway ngf-nginx-gateway-fabric-bb8598998-jwk2m -c nginx
 2024/06/13 20:04:17 [emerg] 27#27: too long parameter, probably missing terminating """ character in /etc/nginx/conf.d/http.conf:78
 ```
 
-##### Access Logs
+1. Access Logs
 
 NGINX access logs record all requests processed by the NGINX server. These logs provide detailed information about each request, which can be useful for troubleshooting and analyzing web traffic.
 Access logs can be viewed with the above method of using `kubectl logs`, or by viewing the access log file directly. To do that, get shell access to your NGINX container using these [steps](#get-shell-access-to-nginx-container). The access logs are located in the file `/var/log/nginx/access.log` in the NGINX container.
 
 You can see logs for a crashed or killed container by adding the `-p` flag to the above commands.
 
-##### Modify Log Levels
+1. Modify Log Levels
 
 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.