nginx · y82 · Jul 23, 2026
@@ -17,7 +17,7 @@ When you have a subscription, you or someone in your organization should have an
 
 That email includes an account name, which is the TENANT_NAME.
 
-To access F5 Distributed Cloud, go to to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with access to NGINX One Console.
+To access F5 Distributed Cloud, go to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with access to NGINX One Console.
 
 If you do not know your TENANT_NAME, you can:
 

@@ -7,7 +7,7 @@ f5-files:
 - content/nic/integrations/app-protect-waf/installation.md
 ---
 
-{{<call-out class="important" title="Admin access required" >}}To complete these steps you need admin access to your cluster. Refer to to your Kubernetes platform's documentation to set up admin access. For Google Kubernetes Engine (GKE), you can refer to their [Role-Based Access Control guide](https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control).{{</call-out>}}
+{{<call-out class="important" title="Admin access required" >}}To complete these steps you need admin access to your cluster. Refer to your Kubernetes platform's documentation to set up admin access. For Google Kubernetes Engine (GKE), you can refer to their [Role-Based Access Control guide](https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control).{{</call-out>}}
 
 1. Create a namespace and a service account:
 

@@ -109,7 +109,7 @@ HTTP basic authentication can be effectively combined with access restriction by
     Access will be granted only for the `192.168.1.1/24` network excluding the `192.168.1.2` address. Note that the `allow` and `deny` directives will be applied in the order they are defined.
 
 2. Combine restriction by IP and HTTP authentication with the [satisfy](https://nginx.org/en/docs/http/ngx_http_core_module.html#satisfy) directive.
-    If you set the directive to to `all`, access is granted if a client satisfies both conditions. If you set the directive to `any`, access is granted if if a client satisfies at least one condition:
+    If you set the directive to `all`, access is granted if a client satisfies both conditions. If you set the directive to `any`, access is granted if if a client satisfies at least one condition:
 
     ```nginx
     location /api {

@@ -292,7 +292,7 @@ You have two options for deploying NGINX Ingress Controller:
 
 ### Set up role-based access control (RBAC) {#set-up-rbac}
 
-{{< call-out class="important" title="Admin access required" >}}To complete these steps you need admin access to your cluster. Refer to to your Kubernetes platform's documentation to set up admin access. For Google Kubernetes Engine (GKE), you can refer to their [Role-Based Access Control guide](https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control).{{</call-out>}}
+{{< call-out class="important" title="Admin access required" >}}To complete these steps you need admin access to your cluster. Refer to your Kubernetes platform's documentation to set up admin access. For Google Kubernetes Engine (GKE), you can refer to their [Role-Based Access Control guide](https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control).{{</call-out>}}
 
 1. Create a namespace and a service account:
 

@@ -177,7 +177,7 @@ This example uses NGINX Open Source as a base: it requires NGINX to be installed
 
 {{< call-out class="note" >}}
 
-If you are not using using `custom_log_format.json` or the IP intelligence feature, you should remove any references to them from your Dockerfile.
+If you are not using `custom_log_format.json` or the IP intelligence feature, you should remove any references to them from your Dockerfile.
 
 {{< /call-out >}}
 
@@ -1039,7 +1039,7 @@ In the same folder as the subscription files, create a _Dockerfile_ based on you
 
 {{< call-out class="note" >}}
 
-If you are not using using `custom_log_format.json` or the IP intelligence feature, you should remove any references to them from your Dockerfile.
+If you are not using `custom_log_format.json` or the IP intelligence feature, you should remove any references to them from your Dockerfile.
 
 {{< /call-out >}}
 

@@ -63,7 +63,7 @@ This example uses NGINX Open Source as a base: it requires NGINX to be installed
 
 {{< call-out class="note" >}}
 
-If you are not using using `custom_log_format.json` or the IP intelligence feature, you should remove any references to them from your Dockerfile.
+If you are not using `custom_log_format.json` or the IP intelligence feature, you should remove any references to them from your Dockerfile.
 
 {{< /call-out >}}