fix wth -> with typo (cloudflare#905)

Author: LeoColomb

products/argo-tunnel/src/content/routing-to-tunnel/kubernetes.md

@@ -27,7 +27,7 @@ Both options rely on Cloudflare's Load Balancer to send traffic for a single hos
 
 3. Create a service that represents your application. In doing so, updates to the application do not impact the Tunnel configuration. For example, an `httpbin` service can be used.
 
-4. Create two deployments wth one replica each using `cloudflared`. Configure `cloudflared` to point to the service IP of the upstream service. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
+4. Create two deployments with one replica each using `cloudflared`. Configure `cloudflared` to point to the service IP of the upstream service. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
 
 5. In the Cloudflare dashboard, create a Load Balancer pool and [point the pool](/routing-to-tunnel/lb) to the two or more Argo Tunnel connections.
 
@@ -39,6 +39,6 @@ Once configured, you can update `cloudflared` by updating one deployment and the
 
 2. Upload the credentials file for each Tunnel as k8s secrets.
 
-3. Create two deployments wth one replica each using `cloudflared`. Configure `cloudflared` to point to an ingress controller. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
+3. Create two deployments with one replica each using `cloudflared`. Configure `cloudflared` to point to an ingress controller. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
 
 4. In the Cloudflare dashboard, create a Load Balancer pool and [point the pool](/routing-to-tunnel/lb) to the two or more Argo Tunnel connections.

products/cloudflare-one/src/content/connections/connect-apps/routing-to-tunnel/kubernetes.md

@@ -21,7 +21,7 @@ Both options rely on Cloudflare's Load Balancer to send traffic for a single hos
 
 3. Create a service that represents your application. In doing so, updates to the application do not impact the Tunnel configuration. For example, an `httpbin` service can be used.
 
-4. Create two deployments wth one replica each using `cloudflared`. Configure `cloudflared` to point to the service IP of the upstream service. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
+4. Create two deployments with one replica each using `cloudflared`. Configure `cloudflared` to point to the service IP of the upstream service. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
 
 5. In the Cloudflare dashboard, create a Load Balancer pool and [point the pool](/connections/connect-apps/routing-to-tunnel/lb) to the two or more Argo Tunnel connections.
 
@@ -33,6 +33,6 @@ Once configured, you can update `cloudflared` by updating one deployment and the
 
 2. Upload the credentials file for each Tunnel as k8s secrets.
 
-3. Create two deployments wth one replica each using `cloudflared`. Configure `cloudflared` to point to an ingress controller. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
+3. Create two deployments with one replica each using `cloudflared`. Configure `cloudflared` to point to an ingress controller. Mount the secrets created in Step 1 and point `cloudflared` to the right path.
 
 4. In the Cloudflare dashboard, create a Load Balancer pool and [point the pool](/connections/connect-apps/routing-to-tunnel/lb) to the two or more Argo Tunnel connections.