Skip to content

Commit 42d0491

Browse files
salonichf5sjberman
andauthored
Update site/content/how-to/monitoring/troubleshooting.md
Co-authored-by: Saylor Berman <[email protected]>
1 parent a664d53 commit 42d0491

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ You can see logs for a crashed or killed container by adding the `-p` flag to th
125125

126126
##### NGINX Gateway Fabric Pod is not running or ready
127127

128-
To understand why NGINX Gateway Fabric Pod has not started running or is not ready, first step is to check the state of the pod to get a detailed information about the current status and events happening in the pod. To do this, use `kubectl describe`:
128+
To understand why the NGINX Gateway Fabric Pod has not started running or is not ready, the first step is to check the state of the Pod to get detailed information about the current status and events happening in the Pod. To do this, use `kubectl describe`:
129129

130130
```shell
131131
kubectl describe pod <ngf-pod-name> [-n namespace]

0 commit comments

Comments
 (0)