fix(tuto): typos (#4673)

Author: nerda-codes

tutorials/deploy-automate-mkdocs-site/index.mdx

@@ -64,14 +64,14 @@ Statements allow you to define who can perform what actions on your bucket. In t
     - Select `Applications` in the **Principals** drop-down.
     - Select your IAM application (`doc website GitHub Actions`) in the **Applications** drop-down.
     - Select `s3:PutObject` in the **Actions** drop-down.
-    - Enter `*` in the the **Resource** field.
+    - Enter `*` in the **Resource** field.
 
 7. Click **+ Add statement** again. We are defining the statement that grants public read access to your website's content:
 
     - Enter a unique statement ID describing the purpose of the statement. For example `Grant public read access to website`.
     - Select `All principals (*)` in the **Principals** drop-down.
     - Select `s3:GetObject` in the **Actions** drop-down.
-    - Enter `*` in the the **Resource** field. This allows anyone to read objects from your bucket.
+    - Enter `*` in the **Resource** field. This allows anyone to read objects from your bucket.
 8. Click **Save changes**.
 
 ## Setting up your GitHub repository
@@ -147,7 +147,7 @@ In this section, we will be adding the following values (secrets) in our GitHub
 
 1. Access your GitHub repository.
 2. Click the **Settings** tab.
-3. Click the **Secrets and varaibles** section, then click **Actions**. You are redirected to the **Secrets** tab.
+3. Click the **Secrets and variables** section, then click **Actions**. You are redirected to the **Secrets** tab.
 4. Click **New repository secret**.
 5. Enter a name and a secret for each of the values listed above. For example, enter `DOC_ACCESS_KEY` in the **Name** field, and `SCWXXXXXXXXXXXXXXXXX` in the **Secret** field.
 6. Click **Add secret** and repeat the operation for the other 3 secrets.
@@ -188,4 +188,4 @@ GitHub Actions will:
 
 If you expect high traffic, consider using our [Edge Services](/edge-services/quickstart/) solution for caching.
 
-If you have a custom domain, you can link it to your documentation website in your `mkdocs.yml` file.
+If you have a custom domain, you can link it to your documentation website in your `mkdocs.yml` file.