address comments

Author: salonichf5

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

@@ -137,7 +137,7 @@ The Pod description includes details about the image name, tags, current status,
 Containers:
   nginx-gateway:
     Container ID:  containerd://06c97a9de938b35049b7c63e251418395aef65dd1ff996119362212708b79cab
-    Image:         nginx-gateway-fabric:sa.choudhary
+    Image:         nginx-gateway-fabric
     Image ID:      docker.io/library/import-2024-06-13@sha256:1460d63bd8a352a6e455884d7ebf51ce9c92c512cb43b13e44a1c3e3e6a08918
     Ports:         9113/TCP, 8081/TCP
     Host Ports:    0/TCP, 0/TCP
@@ -152,7 +152,7 @@ Containers:
       POD_NAME:       ngf-nginx-gateway-fabric-66dd665756-zh7d7 (v1:metadata.name)
   nginx:
     Container ID:   containerd://c2f3684fd8922e4fac7d5707ab4eb5f49b1f76a48893852c9a812cd6dbaa2f55
-    Image:          nginx-gateway-fabric/nginx:sa.choudhary
+    Image:          nginx-gateway-fabric/nginx
     Image ID:       docker.io/library/import-2024-06-13@sha256:c9a02cb5665c6218373f8f65fc2c730f018d0ca652ae827cc913a7c6e9db6f45
     Ports:          80/TCP, 443/TCP
     Host Ports:     0/TCP, 0/TCP
@@ -165,78 +165,25 @@ Events:
   Type    Reason     Age   From               Message
   ----    ------     ----  ----               -------
   Normal  Scheduled  40s   default-scheduler  Successfully assigned nginx-gateway/ngf-nginx-gateway-fabric-66dd665756-zh7d7 to kind-control-plane
-  Normal  Pulled     40s   kubelet            Container image "nginx-gateway-fabric:sa.choudhary" already present on machine
+  Normal  Pulled     40s   kubelet            Container image "nginx-gateway-fabric" already present on machine
   Normal  Created    40s   kubelet            Created container nginx-gateway
   Normal  Started    39s   kubelet            Started container nginx-gateway
-  Normal  Pulled     39s   kubelet            Container image "nginx-gateway-fabric/nginx:sa.choudhary" already present on machine
+  Normal  Pulled     39s   kubelet            Container image "nginx-gateway-fabric/nginx" already present on machine
   Normal  Created    39s   kubelet            Created container nginx
   Normal  Started    39s   kubelet            Started container nginx
 ```
 
 
 ### Modify logging levels
 
-To debug NGINX Gateway Fabric, enable verbose logging by editing the `NginxGateway` configuration. This can be done either before or after deploying NGINX Gateway Fabric.
-
-#### Modify log levels before deploying
-
-1. If using manifests, edit `deploy/manifests/nginx-gateway.yaml` to update the logging level for `nginx-gateway-config`:
-
-```yaml
-apiVersion: gateway.nginx.org/v1alpha1
-kind: NginxGateway
-metadata:
-  name: nginx-gateway-config
-  namespace: nginx-gateway
-  labels:
-    app.kubernetes.io/name: nginx-gateway
-    app.kubernetes.io/instance: nginx-gateway
-    app.kubernetes.io/version: "edge"
-spec:
-  logging:
-    level: debug
-```
-
-1. If using helm, add `--set nginxGateway.config.logging.level=<log-level>` to your helm installation command.
-
-#### Modify log levels after deploying
-
-Once you have deployed NGINX Gateway Fabric, you can modify log levels by editing the config for NGINX Gateway as shown below:
-
-```shell
-kubectl [-n namespace] edit nginxgateways ngf-config
-```
-
-```yaml
-apiVersion: gateway.nginx.org/v1alpha1
-kind: NginxGateway
-metadata:
-  annotations:
-    meta.helm.sh/release-name: ngf
-    meta.helm.sh/release-namespace: nginx-gateway
-  creationTimestamp: "2024-06-12T18:35:05Z"
-  generation: 1
-  labels:
-    app.kubernetes.io/instance: ngf
-    app.kubernetes.io/managed-by: Helm
-    app.kubernetes.io/name: nginx-gateway-fabric
-    app.kubernetes.io/version: edge
-    helm.sh/chart: nginx-gateway-fabric-1.3.0
-  name: ngf-config
-  namespace: nginx-gateway
-  resourceVersion: "62293"
-  uid: fa6d6a12-14e1-4168-95d5-595e7f63b270
-spec:
-  logging:
-    level: debug
-```
+To debug NGINX Gateway Fabric, enable verbose logging by editing the `NginxGateway` configuration. This can be done either before or after deploying NGINX Gateway Fabric. Please refer to this [guide](https://docs.nginx.com/nginx-gateway-fabric/how-to/configuration/control-plane-configuration) to do so.
 
 ### NGINX fails to reload
 
 #### Description
 
 NGINX reload errors can occur for various reasons, including syntax errors in configuration files, permission issues, and more. To determine if NGINX has failed to reload, check logs for your _nginx-gateway_ and _nginx_ containers.
-You will see the following error in the _nginx-gateway_  logs `failed to reload NGINX:` followed by the reason for the failure. Similarly, you will see error logs in the _nginx_ container as `2024/06/12 14:25:11 [emerg] 12345#0: open() "/var/run/nginx.pid" failed (13: Permission denied)`.
+You will see the following error in the _nginx-gateway_  logs `failed to reload NGINX:` followed by the reason for the failure. Similarly, error logs in _nginx_ container start with `emerg`. For example, `2024/06/12 14:25:11 [emerg] 12345#0: open() "/var/run/nginx.pid" failed (13: Permission denied)` shows a critical error, such as a permission problem preventing NGINX from accessing necessary files.
 
 To debug why your reload has failed, start with verifying the syntax of your configuration files by opening a shell in the NGINX container following these [steps](#get-shell-access-to-containers) and running `nginx -T`. If there are errors in your configuration file, the reload will fail and specify why it has failed.