Removed duplicate words.

2026-09-25 04:28:15 +00:00 · 2019-05-15 10:15:10 -07:00
parent 5eb534e584
commit 144ae56ae3
12 changed files with 14 additions and 14 deletions
@@ -15,7 +15,7 @@ rancher:
      auth: dXNlcm5hbWU6cGFzc3dvcmQ=
 ```

-The `auth` key is generated by base64 encoding a string of the form `username:password`. The `docker login` command can be be used to generate an `auth` key. After running the command and authenticating successfully, the key can be found in the `$HOME/.docker/config.json` file.
+The `auth` key is generated by base64 encoding a string of the form `username:password`. The `docker login` command can be used to generate an `auth` key. After running the command and authenticating successfully, the key can be found in the `$HOME/.docker/config.json` file.

 ```json
 {
@@ -11,7 +11,7 @@ After you configure external authentication, the users that display on the **Use

 - If you are logged in as a local user, only local users display.

- If you are logged in an an external user, both external and local users display.
+- If you are logged in an external user, both external and local users display.

 ## Users and Roles

@@ -28,7 +28,7 @@ Use {{< product >}} to create a Kubernetes cluster in Azure.

 		{{< step_create-cloud-credential >}}

-		- **Placement** sets the geographical region where where your cluster is hosted and other location metadata.
+		- **Placement** sets the geographical region where your cluster is hosted and other location metadata.

 		- **Network** configures the networking used in your cluster.

@@ -198,7 +198,7 @@ If you are using a Certificate Signed By A Recognized Certificate Authority, you

 ## 8. Configure FQDN

-There is one reference to `<FQDN>` in the RKE config file. Replace this reference with the FQDN you chose in in [3. Configure DNS](#3-configure-dns).
+There is one reference to `<FQDN>` in the RKE config file. Replace this reference with the FQDN you chose in [3. Configure DNS](#3-configure-dns).

 1. Open `rancher-cluster.yml`.

@@ -97,7 +97,7 @@ For production environments, you also have the option of using [Let's Encrypt](h
 >- Open port `TCP/80` on your Linux host. The Let's Encrypt http-01 challenge can come from any source IP address, so port `TCP/80` must be open to all IP addresses.


-After you fulfill the prerequisites, you can install Rancher using a Let's Encrypt certificate by running the following command. Replace `<YOUR.DNS.NAME>` with your your domain.
+After you fulfill the prerequisites, you can install Rancher using a Let's Encrypt certificate by running the following command. Replace `<YOUR.DNS.NAME>` with your domain.

 	docker run -d --restart=unless-stopped \
 	  -p 80:80 -p 443:443 \
@@ -4,7 +4,7 @@ weight: 252
 aliases:
 - /rancher/v2.x/en/installation/single-node-install-external-lb/
 ---
-For development and testing environments that have a special requirement to terminate TLS/SSL at a load balancer instead of your Rancher Server container, deploy Rancher and configure a load balancer to work with it it conjunction. This install procedure walks you through deployment of Rancher using a single container, and then provides a sample configuration for a layer 7 Nginx load balancer.
+For development and testing environments that have a special requirement to terminate TLS/SSL at a load balancer instead of your Rancher Server container, deploy Rancher and configure a load balancer to work with it conjunction. This install procedure walks you through deployment of Rancher using a single container, and then provides a sample configuration for a layer 7 Nginx load balancer.

 >**Want to skip the external load balancer?**
 > See [Single Node Installation]({{< baseurl >}}/rancher/v2.x/en/installation/single-node) instead.
@@ -405,7 +405,7 @@ spec:
 1. Test that pod autoscaling works as intended.<br/></br>
  **To Test Autoscaling Using Resource Metrics:**
  {{% accordion id="observe-upscale-2-pods-cpu" label="Upscale to 2 Pods: CPU Usage Up to Target" %}}
-Use your load testing tool to to scale up to two pods based on CPU Usage.
+Use your load testing tool to scale up to two pods based on CPU Usage.

 1. View your HPA.
    ```
@@ -491,7 +491,7 @@ Use your load testing tool to upspace to 3 pods based on CPU usage with `horizon
      ```
  {{% /accordion %}}
  {{% accordion id="observe-downscale-1-pod" label="Downscale to 1 Pod: All Metrics Below Target" %}}
-Use your load testing to to scale down to 1 pod when all metrics are below target for `horizontal-pod-autoscaler-downscale-delay` (5 minutes by default).
+Use your load testing to scale down to 1 pod when all metrics are below target for `horizontal-pod-autoscaler-downscale-delay` (5 minutes by default).

 1. Enter the following command.
  ```
@@ -794,7 +794,7 @@ To create HPA resources based on resource metrics such as CPU and memory use, yo
    ```
    # kubectl -n kube-system logs metrics-server-6fbfb84cdd-t2fk9
    ```
-    Then review the log to confirm that that the `metrics-server` package is running.
+    Then review the log to confirm that the `metrics-server` package is running.
    {{% accordion id="metrics-server-run-check" label="Metrics Server Log Output" %}}
    I0723 08:09:56.193136       1 heapster.go:71] /metrics-server --source=kubernetes.summary_api:''
    I0723 08:09:56.193574       1 heapster.go:72] Metrics Server version v0.2.1
@@ -28,7 +28,7 @@ Create a new namespace to isolate apps and resources in a project.

 1. From the **Global** view, open the project where you want to create a namespace.

-    >**Tip:** As a best practice, we recommend creating namespaces from the project level. However, cluster owners and members can can create them from the cluster level as well.
+    >**Tip:** As a best practice, we recommend creating namespaces from the project level. However, cluster owners and members can create them from the cluster level as well.

 1. From the main menu, select **Namespace**. The click **Add Namespace**.

@@ -30,7 +30,7 @@ This section contains information to help you troubleshoot issues when using Ran

 - [Rancher HA]({{< baseurl >}}/rancher/v2.x/en/troubleshooting/rancherha/)

-    If you experience issues issues with your [High Availability (HA) Install]({{< baseurl >}}/rancher/v2.x/en/installation/ha/)
+    If you experience issues with your [High Availability (HA) Install]({{< baseurl >}}/rancher/v2.x/en/installation/ha/)

 - [Imported clusters]({{< baseurl >}}/rancher/v2.x/en/troubleshooting/imported-clusters/)

@@ -18,7 +18,7 @@ RKE only adds additional add-ons when using `rke up` multiple times. RKE does **

 As of v0.1.8, RKE will update an add-on if it is the same name.

-Prior to v0.1.8, update any add-ons by by using `kubectl edit`.
+Prior to v0.1.8, update any add-ons by using `kubectl edit`.


 ## Critical and Non-Critical Add-ons
@@ -18,7 +18,7 @@ RKE only adds additional add-ons when using `rke up` multiple times. RKE does **

 As of v0.1.8, RKE will update an add-on if it is the same name.

-Prior to v0.1.8, update any add-ons by by using `kubectl edit`.
+Prior to v0.1.8, update any add-ons by using `kubectl edit`.

 ## In-line Add-ons

@@ -99,7 +99,7 @@ rpm -q docker-ce
 When using the upstream Docker packages, please follow [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user).

 #### Using RHEL/CentOS packaged Docker
-If you are using the Docker Docker package supplied by Red Hat / CentOS, the package name is `docker`. You can check the installed package by executing:
+If you are using the Docker package supplied by Red Hat / CentOS, the package name is `docker`. You can check the installed package by executing:

 ```
 rpm -q docker