Apply suggestions from code review

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

Author: 3 people

pages/kubernetes/how-to/access-kubernetes-dashboard.mdx

@@ -23,7 +23,7 @@ categories:
 
 1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Kubernetes Kapsule overview displays.
 2. From the drop-down menu, select the geographical region you want to manage.
-3. Click the name of the cluster you want to access. The cluster overview page displays. This page provides several pieces of information about your cluster:
+3. Click the name of the cluster you want to access. The cluster overview page displays. This page provides several pieces of information about your cluster.
 4. Click **Dashboard**. You are taken to your cluster's Kubernetes dashboard.
    Here, you can troubleshoot your containerized application, manage the cluster resources, get an overview of applications running on your cluster, and create or modify certain resources.
 

pages/kubernetes/how-to/deploy-ingress-controller.mdx

@@ -31,5 +31,3 @@ An [ingress controller](/kubernetes/concepts/#ingress-controller) is an entry po
    </Message>
 6. Assign a name and namespace for your application.
 7. Click **Deploy application** to initiate the deployment of your ingress controller.
-
-

pages/kubernetes/how-to/migrate-ent1-pools-to-pop2.mdx

@@ -27,7 +27,7 @@ This guide provides a step-by-step process to migrate from **ENT1** Instances to
 1. Log in to the [Scaleway Console](https://console.scaleway.com).
 2. Navigate to **Kubernetes** under the **Containers** section in the side menu of the console.
 3. From the drop-down menu, select the geographical region you want to manage.
-3. Select the cluster containing the ENT1 pools you intend to migrate.
+4. Select the cluster containing the ENT1 pools you intend to migrate.
 5. In the **Pools** tab, identify and note the pools using **ENT1** Instances.
 
 ## Creating equivalent POP2 pools

pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx

@@ -76,8 +76,6 @@ The GPU operator on your Scaleway node pools is fully configurable through the E
 5. Click <Icon name="more" /> > **Edit** next to the GPU operator deployment. A pop-up displays.
 6. Edit the YAML configuration of the deployment to match your desired configuration.
     <Message type="tip">
-        Refer to the [offical NVIDIA documentation](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/getting-started.html#chart-customization-options) for a list of available Helm configuration options.
+        Refer to the [official NVIDIA documentation](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/getting-started.html#chart-customization-options) for a list of available Helm configuration options.
     </Message>
 7. Click **Update and deploy** to update and deploy the configuration of the GPU operator.
-
-