Merge branch 'main' into otel

Author: y82

.github/CODEOWNERS

@@ -30,8 +30,8 @@ content/nap-waf/*           @nginx/nap-docs-approvers
 data/nap-waf/*              @nginx/nap-docs-approvers
 
 # NGINXaaS for Azure 
-content/nginxaas-azure/*          @nginx/n4a-docs
-content/includes/nginxaas-azure/* @nginx/n4a-docs
+content/nginxaas-azure/*          @nginx/n4a-docs-approvers
+content/includes/nginxaas-azure/* @nginx/n4a-docs-approvers
 
 # NGINX Gateway Fabric
 content/ngf/*               @nginx/nginx-gateway-fabric

content/ngf/how-to/data-plane-configuration.md

@@ -199,7 +199,7 @@ spec:
       mode: ProxyProtocol
       trustedAddresses:
       - type: CIDR
-        value "76.89.90.11/24"
+        value: "76.89.90.11/24"
 EOF
 ```
 

content/nim/admin-guide/license/report-usage-connected-deployment.md

@@ -39,7 +39,7 @@ To allow NGINX Instance Manager to report usage data to F5, make sure port `443`
 
 ### Configure NGINX Plus to report usage to NGINX Instance Manager
 
-To configure NGINX Plus (R33 and later) to report usage data to NGINX Instance Manger:
+To configure NGINX Plus (R33 and later) to report usage data to NGINX Instance Manager:
 
 {{< include "licensing-and-reporting/configure-nginx-plus-report-to-nim.md" >}}
 
@@ -74,4 +74,4 @@ If you prefer submitting usage reports to F5 manually, follow these steps:
 
 ## Error log location and monitoring {#log-monitoring}
 
-{{< include "licensing-and-reporting/log-location-and-monitoring.md" >}}
+{{< include "licensing-and-reporting/log-location-and-monitoring.md" >}}

content/nim/deploy/vm-bare-metal/install-nim-deprecated.md

@@ -278,7 +278,7 @@ To install NGINX Instance Manager, you need to add the official repository to pu
 {{<tabs name="upgrade_nim">}}
 {{%tab name="CentOS, RHEL, RPM-Based"%}}
 
-1. To upgrade to the latest version of the Instance Manger, run the following command:
+1. To upgrade to the latest version of the Instance Manager, run the following command:
 
    ```bash
    sudo yum update -y nms-instance-manager

content/nim/disconnected/report-usage-disconnected-deployment.md

@@ -25,7 +25,7 @@ Before submitting usage data to F5, first configure NGINX Plus to report telemet
 
 ### Configure NGINX Plus to report usage to NGINX Instance Manager
 
-To configure NGINX Plus (R33 and later) to report usage data to NGINX Instance Manger:
+To configure NGINX Plus (R33 and later) to report usage data to NGINX Instance Manager:
 
 {{< include "licensing-and-reporting/configure-nginx-plus-report-to-nim.md" >}}
 
@@ -182,4 +182,4 @@ To upload the the usage acknowledgement:
 
 ## Error log location and monitoring {#log-monitoring}
 
-{{< include "licensing-and-reporting/log-location-and-monitoring.md" >}}
+{{< include "licensing-and-reporting/log-location-and-monitoring.md" >}}

content/nim/system-configuration/secure-traffic.md

@@ -136,7 +136,7 @@ To generate the necessary certificates, follow these steps. You can modify these
     }
 
     make_server() {
-        echo "Creating nginx-manger certificate and key"
+        echo "Creating nginx-manager certificate and key"
         openssl req \
             -new \
             -nodes \

content/nms/acm/tutorials/aws-deploy.md

@@ -227,7 +227,7 @@ Follow the steps in the [Set Up a Developer Portal Environment]({{< ref "/nms/ac
 
 ## Terminal Access Using Session Manager (Optional) {#session-manager}
 
-AWS allows you to enable SSH traffic to a specific Source IP Address which is much safer than exposing it to everyone on the internet. Even though exposing it to one IP may be good enough, it might not be sufficient for your company policy. It is possible to completely disable SSH traffic yet still have terminal access to your EC2 Instances. There are different ways of doing this, and one way covered here is using [AWS System Manager Session Manger](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html).
+AWS allows you to enable SSH traffic to a specific Source IP Address which is much safer than exposing it to everyone on the internet. Even though exposing it to one IP may be good enough, it might not be sufficient for your company policy. It is possible to completely disable SSH traffic yet still have terminal access to your EC2 Instances. There are different ways of doing this, and one way covered here is using [AWS System Manager Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html).
 
 There are two methods of gaining terminal access via Session Manager:
 

content/solutions/about-subscription-licenses.md

@@ -88,7 +88,7 @@ In environments where NGINX Plus instances cannot access the internet, you'll ne
 
 #### Configure NGINX Plus to report usage to NGINX Instance Manager
 
-To configure NGINX Plus R33 or later to report usage data to NGINX Instance Manger:
+To configure NGINX Plus R33 or later to report usage data to NGINX Instance Manager:
 
 {{< include "licensing-and-reporting/configure-nginx-plus-report-to-nim.md" >}}
 
@@ -162,7 +162,7 @@ For detailed instructions on installing or upgrading NGINX App Protect DoS, visi
 ## Watch instructional videos
 
 ### Submit usage reports in a connected environment
-{{< youtube id="mnTJ1oYnZpk" >}}
+{{< youtube id="PDnacyh2RUw" >}}
 
 ### Submit usage reports in a disconnected environment
 {{< youtube id="4wIM21bR9-g" >}}