Apply suggestions from code review

Author: bene2k1

tutorials/terraform-dynamic-gitlab-runner/index.mdx

@@ -14,9 +14,7 @@ import Requirements from '@macros/iam/requirements.mdx'
 GitLab runners are the components that execute the jobs defined in your GitLab CI/CD pipelines. They can be installed on various operating systems and can run jobs on different platforms. Runners can be configured to be specific to a project or shared across multiple projects.
 With terraform Scaleway provider and GitLab one, runners can be dynamically created and destroyed.
 
-## Before you start
-
-To complete the actions presented below, you must have:
+<Requirements />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
@@ -27,19 +25,19 @@ To complete the actions presented below, you must have:
 
 ### Gitlab setup
 
-he following GitLab CI/CD needs 3 secret variables :
+The following GitLab CI/CD needs 3 secret variables:
 - GITLAB_TOKEN
 - SCW_SECRET_KEY
 - SCW_ACCES_KEY
 
-The `GITLAB_TOKEN` needs to be a GitLab personal access token with the Owner role, and create_runner scope.
+The `GITLAB_TOKEN` needs to be a GitLab personal access token with the **Owner** role, and `create_runner` scope.
 Create the environment variables in your [project cicd settings](https://docs.gitlab.com/ci/variables/)
 
 ### terraform setup
 
-First we have to provide a basic terraform setup : 
+Start by providing a basic Terraform setup: 
 
-1. Create the main.tf file :
+1. Create the `main.tf` file:
         ```hcl
         //providers
         terraform {
@@ -110,7 +108,7 @@ First we have to provide a basic terraform setup :
             value = gitlab_user_runner.project_runner.id
         }
         ```
-2. Create the var.tf file :
+2. Create the `var.tf` file:
         ```hcl
         variable "project_id" {
             type        = string
@@ -169,7 +167,7 @@ First we have to provide a basic terraform setup :
             description = "volume in Gb"
         }
         ```
-3. Create the cloud-init.yml file :
+3. Create the `cloud-init.yml` file:
         ```yml
         #cloud-config
         package_update: true
@@ -270,7 +268,7 @@ First we have to provide a basic terraform setup :
                 - terraform init -var-file="env.tfvars"
                 - terraform apply -destroy -var-file="env.tfvars" -auto-approve
         ```
-2. Create the look.bash file :
+2. Create the `look.bash` file:
         ```bash
         #!/bin/bash
 
@@ -300,12 +298,12 @@ First we have to provide a basic terraform setup :
         done
         ```
 
-With this setup the Gitlab-CI/CD create an instance and register it as a GitLab runner, run the work job on the instance, then delete the instance and the runner.
-This setup allows you to dynamically provide high computation runners in a cost-effective way. You can also customize the cloud init to fit your business needs, such as connecting to your company VPN.
+With this setup, GitLab-CI/CD creates an Instance and registers it as a GitLab runner, runs the workload on the Instance, then deletes the Instance and the runner.
+This setup allows you to dynamically provide high-computation runners in a cost-effective way. You can also customize the cloud init to fit your business needs, such as connecting to your company's VPN.
 
 ## Going further
 
-If you want to use a custom instance image, you can edit the `main.tf` file as bellow :
+If you want to use a custom Instance image, you can edit the `main.tf` file as below:
 
         ```hcl
         // ... previous code