removed extra the and fixed hyperlinks

Author: dkleinF5

content/waf/install/docker.md

@@ -70,7 +70,7 @@ The steps you should follow on this page are dependent on your configuration typ
 
 You will need Docker registry credentials to access private-registry.nginx.com for the Multi-container or Hybrid deployment options.
 
-Create a directory and copy your [certificate and key]({{< ref "/waf/install/docker.md#Shared Requirements" >}}) to this directory:
+Create a directory and copy your certificate and key to this directory:
 
 ```shell
 mkdir -p /etc/docker/certs.d/private-registry.nginx.com

content/waf/install/kubernetes-plm.md

@@ -44,7 +44,7 @@ To complete this guide, you will need the following prerequisites:
 - An active F5 WAF for NGINX subscription in [MyF5](https://my.f5.com/manage/s/) (Purchased or trial).
   - Download the [SSL certificate and private key file](#general-subscription-credentials-needed-for-deployments) associated with your 5 NGINX App Protect WAF subscription from the MyF5 Customer Portal if you do not plan of using NGINX Plus in your deployment.
   - Download the [SSL certificate and private key file](#general-subscription-credentials-needed-for-deployments), and the [JWT license](#additional-subscription-credentials-needed-for-a-deployments-with-nginx-plus) file associated with your NGINX Plus subscription from the MyF5 Customer Portal if you plan of using NGINX Plus in your deployment.
-- [Docker registry credentials](#Additional subscription credentials needed for deployments) are needed to access private-registry.nginx.com
+- [Docker registry credentials](#additional-subscription-credentials-needed-for-deployments) are needed to access private-registry.nginx.com
 
 ## Default security policy and logging profile
 
@@ -1018,7 +1018,7 @@ cd nginx-app-protect
 kubectl apply -f crds/
 ```
 
-Finish the the process by using `helm upgrade`:
+Finish the process by using `helm upgrade`:
 
 ```shell
 helm upgrade <release-name> . \

content/waf/policies/bot-signatures.md

@@ -18,7 +18,7 @@ This feature is enabled by default with the `bot-defense` parameter, and include
 
 ## Bot signatures
 
-Bot signature detection works by inspecting the the User-Agent header and URI of a request.
+Bot signature detection works by inspecting the User-Agent header and URI of a request.
 
 Each detected bot signature belongs to a bot class: search engine signatures such as `googlebot` are under the trusted_bots class, but F5 WAF for NGINX performs additional checks to authenticate a trusted bot.