Merge branch 'main' into nic/otel-instructions

Author: ADubhlaoich

content/nic/logging-and-monitoring/opentelemetry.md

@@ -30,7 +30,7 @@ The following is an example of a OpenTelemetry collector running in your cluster
 otel-exporter-endpoint: "http://otel-collector.default.svc.cluster.local:4317"
 ```
 
-A complete ConfigMap example with all OpenTelemetry map options could look as follows:
+A complete ConfigMap example with all OpenTelemetry options could look as follows:
 
 {{< ghcode "https://raw.githubusercontent.com/nginx/kubernetes-ingress/refs/heads/main/examples/shared-examples/otel/nginx-config.yaml" >}}
 
@@ -52,7 +52,7 @@ otel-trace-in-http: "true"
 
 You can configure OpenTelemetry on a per resource basis in NGINX Ingress Controller.
 
-For this functionality, you must [enable snippets]({{< ref "/nic/configuration/ingress-resources/advanced-configuration-with-snippets.md" >}}), using the `-enable-snippets` command-line argument.
+For this functionality, you must [enable snippets]({{< ref "/nic/configuration/ingress-resources/advanced-configuration-with-snippets.md" >}}) with the `-enable-snippets` command-line argument.
 
 Based on the state of global configuration, you can selectively enable or disable metrics for each resource.
 

content/nic/releases.md

@@ -48,7 +48,7 @@ Lastly, in our previous v5.0.0 release, we removed support for OpenTracing. This
 [GitHub Container](https://github.com/nginx/kubernetes-ingress/pkgs/container/kubernetes-ingress),
 [Amazon ECR Public Gallery](https://gallery.ecr.aws/nginx/nginx-ingress) or [Quay.io](https://quay.io/repository/nginx/nginx-ingress).
 - For NGINX Plus, use the 5.1.0 images from the F5 Container registry or build your own image using the 5.1.0 source code
-- For Helm, use version 2.2.0 of the chart.
+- For Helm, use version 2.2.1 of the chart.
 
 ### <i class="fa-solid fa-life-ring"></i> Supported Platforms