docs(tuto): review jess

Co-authored-by: Jessica <[email protected]>

Author: nerda-codes

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

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to build and deploy an MkDocs site using GitHub Actions for CI/CD automation. Streamline your workflow with this step-by-step guide.
 categories:
   - object-storage
-tags: mkdocs-deployment deploy-mkdocs-site mkdocs-automation static-site mkdocs-ci-cd github-workflow-mkdocs
+tags: mkdocs deployment automation static-site ci-cd github
 dates:
   validation: 2025-03-13
   posted: 2025-03-13
@@ -51,8 +51,7 @@ This tutorial is the second in a series on building and deploying websites using
 
 ## Adding statements to your bucket policy
 
-Statements allow you to define who can perform what actions on your bucket. In this section, we will add a statement to allow your IAM application to push content to your bucket, and
-another one that grants public read access to your website's content.
+Statements allow you to define who can perform what actions on your bucket. In this section, we will add a statement to allow your IAM application to push content to your bucket, and another one that grants public read access to your website's content.
 
 1. From the Scaleway console side-menu, click **Storage**, then click **Object Storage**.
 2. Click your bucket, then click the **Bucket settings** tab.
@@ -139,7 +138,7 @@ jobs:
 
 ## Adding your secrets in GitHub
 
-In this section we will be adding the following values (secrets) in our GitHub repository. This will alloy the GitHub Actions workflow to access your bucket using the information in the `deploy-docs.yml` file.
+In this section, we will be adding the following values (secrets) in our GitHub repository. This will allow the GitHub Actions workflow to access your bucket using the information in the `deploy-docs.yml` file.
 
 - `DOC_ACCESS_KEY`: Your Scaleway API access key.
 - `DOC_SECRET_KEY`: Your Scaleway API secret key.
@@ -153,7 +152,6 @@ In this section we will be adding the following values (secrets) in our GitHub r
 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.
 
-
 ## Deploying your documentation
 
 1. Make sure that the **only action** in the statement to grant read access to your bucket is `s3:GetObject`. Your statement should look like the following: