docs: remove repetitive words

Documentation fixes.

Signed-off-by: goodmost <zhaohaiyang@outlook.com>

website/content/v0.10/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.11/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.12/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.13/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.14/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.6/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.7/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.8/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v0.9/guides/managing-pki.md

@@ -7,7 +7,7 @@ description: ""
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -31,7 +31,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v1.0/talos-guides/configuration/managing-pki.md

@@ -9,7 +9,7 @@ aliases:
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -33,7 +33,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v1.1/talos-guides/configuration/managing-pki.md

@@ -9,7 +9,7 @@ aliases:
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -33,7 +33,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v1.2/talos-guides/configuration/managing-pki.md

@@ -9,7 +9,7 @@ aliases:
 
 In order to create a key pair, you will need the root CA.
 
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash
@@ -33,7 +33,7 @@ In order to renew the certificate, you will need the root CA, and the admin priv
 The base64 encoded key can be found in any one of the control plane node's configuration file.
 Where it is exactly will depend on the specific version of the configuration file you are using.
 
-Save the the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
+Save the CA public key, CA private key, and admin private key as `ca.crt`, `ca.key`, and `admin.key` respectively.
 Now, run the following commands to generate a certificate:
 
 ```bash

website/content/v1.3/talos-guides/configuration/managing-pki.md

@@ -34,7 +34,7 @@ talosctl gen config --with-secrets secrets.yaml --output-types talosconfig -o ta
 
 In order to create a new key pair for client configuration, you will need the root Talos API CA.
 The base64 encoded CA can be found in the control plane node's configuration file.
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
 
 ```shell
 yq eval .machine.ca.crt controlplane.yaml | base64 -d > ca.crt

website/content/v1.4/talos-guides/configuration/managing-pki.md

@@ -34,7 +34,7 @@ talosctl gen config --with-secrets secrets.yaml --output-types talosconfig -o ta
 
 In order to create a new key pair for client configuration, you will need the root Talos API CA.
 The base64 encoded CA can be found in the control plane node's configuration file.
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
 
 ```shell
 yq eval .machine.ca.crt controlplane.yaml | base64 -d > ca.crt

website/content/v1.5/talos-guides/configuration/managing-pki.md

@@ -34,7 +34,7 @@ talosctl gen config --with-secrets secrets.yaml --output-types talosconfig -o ta
 
 In order to create a new key pair for client configuration, you will need the root Talos API CA.
 The base64 encoded CA can be found in the control plane node's configuration file.
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
 
 ```shell
 yq eval .machine.ca.crt controlplane.yaml | base64 -d > ca.crt

website/content/v1.6/talos-guides/configuration/managing-pki.md

@@ -34,7 +34,7 @@ talosctl gen config --with-secrets secrets.yaml --output-types talosconfig -o ta
 
 In order to create a new key pair for client configuration, you will need the root Talos API CA.
 The base64 encoded CA can be found in the control plane node's configuration file.
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
 
 ```shell
 yq eval .machine.ca.crt controlplane.yaml | base64 -d > ca.crt

website/content/v1.7/talos-guides/howto/cert-management.md

@@ -45,7 +45,7 @@ talosctl gen config --with-secrets secrets.yaml --output-types talosconfig -o ta
 
 In order to create a new key pair for client configuration, you will need the root Talos API CA.
 The base64 encoded CA can be found in the control plane node's configuration file.
-Save the the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
+Save the CA public key, and CA private key as `ca.crt`, and `ca.key` respectively:
 
 ```shell
 yq eval .machine.ca.crt controlplane.yaml | base64 -d > ca.crt