Apply suggestions from code review

Co-authored-by: Jodie Putrino <[email protected]>

Author: mjang

content/nginx-one/changelog.md

@@ -34,7 +34,7 @@ Stay up-to-date with what's new and improved in the F5 NGINX One Console.
 
 ### Monitor F5 NGINX Ingress Controller deployments
 
-You can now montior your NGINX Ingress Controller deployments. For details, see how
+You can now monitor your NGINX Ingress Controller deployments. For details, see how
 you can [Connect to NGINX One Console]({{< ref "/nginx-one/k8s/add-nic.md" >}}).
 
 Unlike other NGINX instances, when you connect NGINX Ingress Controller to NGINX One Console, access is read-only. Refer to our [NGINX Ingress Controller]({{< ref "/nic/" >}}) for details on how to modify these instances.

content/nginx-one/k8s/add-nic.md

@@ -24,7 +24,7 @@ kubectl create secret generic dataplane-key --from-literal=dataplane.key=<Your D
 ```
 
 When you create a Kubernetes Secret, use the same namespace where NGINX Ingress Controller is running. 
-If you use `-watch-namespace` or `watch-secret-namespace` arguments with NGINX Ingress Controller, 
+If you use [`-watch-namespace`]({{< ref "/nic/configuration/global-configuration/command-line-arguments.md#watch-namespace-string" >}}) or [`watch-secret-namespace`]({{< ref "/nic/configuration/global-configuration/command-line-arguments.md#watch-secret-namespace-string" >}}) arguments with NGINX Ingress Controller, 
 you need to add the dataplane key secret to the watched namespaces. This secret will take approximately 60 - 90 seconds to reload on the pod.
 
 {{<note>}}
@@ -45,7 +45,7 @@ nginxAgent:
 ```
 
 The `dataplaneKeySecretName` is used to authenticate the agent with NGINX One Console. See the [NGINX One Console Docs]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}})
-for instructions on to generate your dataplane key from the NGINX One Console.
+for instructions on how to generate your dataplane key from the NGINX One Console.
 
 Follow the [Installation with Helm]({{< ref "/nic/installation/installing-nic/installation-with-helm.md" >}}) instructions to deploy NGINX Ingress Controller.
 
@@ -122,7 +122,7 @@ Follow the [Installation with Manifests]({{< ref "/nic/installation/installing-n
 
 ## Verify a connection to NGINX One Console
 
-After deploying NGINX Ingress Controller or NGINX Gateway Fabric with NGINX Agent, you can verify the connection to NGINX One Console.
+After deploying NGINX Ingress Controller <!-- or NGINX Gateway Fabric --> with NGINX Agent, you can verify the connection to NGINX One Console.
 Log in to your F5 Distributed Console cloud account. Select **NGINX One > Visit Service**. In the dashboard that appears, navigate to **Manage > Instances**. Your instances should appear in the list, where the instance name is the hostname and also the pod name.
 
 ## Troubleshooting

content/nginx-one/k8s/overview.md

@@ -16,5 +16,5 @@ You can now include Kubernetes systems through the [control plane](https://www.f
 
 - Set up a connection to F5 NGINX One Console through a data plane key.
 - Monitor each connected Kubernetes system for CVEs.
-- Review the NGINX Ingress Controller and NGINX Gateway Fabric instances that are part of your fleet
+- Review the NGINX Ingress Controller instances that are part of your fleet.