Re add missing line for N1 Console telemetry (#1309)

* Re add missing line for N1 Console telemetry

* fix: per @bjee19 request

---------

Co-authored-by: Alan Dooley <[email protected]>
Co-authored-by: Mike Jang <[email protected]>

Author: 3 people

content/ngf/overview/product-telemetry.md

@@ -33,14 +33,14 @@ Telemetry data is collected once every 24 hours and sent to a service managed by
 - **Control Plane Pod Count** the count of NGINX Gateway Fabric Pods.
 - **Data Plane Pod Count** the count of NGINX data plane Pods.
 - **NGINX One Console Connection Info** indicates whether the connection to the NGINX One Console is enabled. 
-This data is used to identify the following information:
 
-- The flavors of Kubernetes environments that are most popular among our users.
-- The number of unique NGINX Gateway Fabric installations.
-- The scale of NGINX Gateway Fabric Deployments.
-- The scale of Gateway API resources.
-- The used features of NGINX Gateway Fabric.
-- The cluster is connected to NGINX One Console.
+  This data is used to identify the following information:
+  - The flavors of Kubernetes environments that are most popular among our users.
+  - The number of unique NGINX Gateway Fabric installations.
+  - The scale of NGINX Gateway Fabric Deployments.
+  - The scale of Gateway API resources.
+  - The used features of NGINX Gateway Fabric.
+  - The cluster is connected to NGINX One Console.
 
 Our goal is to publicly discuss data trends to drive roadmap discussions in our [Community Meeting](https://github.com/nginx/nginx-gateway-fabric/discussions/1472).
 
@@ -58,4 +58,4 @@ helm install ... --set nginxGateway.productTelemetry.enable=false
 
 ### Manifests
 
-Add the `--product-telemetry-disable` flag to the `nginx-gateway` container in your Deployment manifest.
+Add the `--product-telemetry-disable` flag to the `nginx-gateway` container in your Deployment manifest.