Apply suggestions from code review

Co-authored-by: ldecarvalho-doc <[email protected]>
Co-authored-by: nerda-codes <[email protected]>
Co-authored-by: Rowena Jones <[email protected]>

Author: 4 people

serverless/containers/how-to/create-a-containers-namespace.mdx

@@ -27,7 +27,7 @@ This page shows you how to create a Serverless Containers namespace. [Namespaces
     - Enter a **name**, and optionally a **description** for your namespace. The name must only contain alphanumeric characters and dashes.
     - Choose a **region**, which is the geographical location in which your namespace will be deployed.
     - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+Add new variable** and enter the key / value pair.
-    - Set secret environment variables (optional). **Secrets** are environment variables which are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**.
+    - Set secret environment variables (optional). **Secrets** are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**.
     - Verify the **estimated cost**.
 4. Click **Create namespace only** to finish, or click **Create namespace and add container** if you want to [deploy a container](/serverless/containers/how-to/deploy-container/) next.
 

serverless/containers/how-to/deploy-container.mdx

@@ -32,16 +32,17 @@ You can deploy a container from the [Scaleway Container Registry](/containers/co
 3. Click **Deploy container**. The container creation wizard displays.
 4. Complete the following steps in the wizard:
     - Select the **Scaleway** Container Registry.
-    - Choose an [image](/serverless/containers/concepts/#image) from your Container Registry. Select the required Container Registry namespace from the drop-down list, and then select the container and tag.
+    - Choose an [image](/serverless/containers/concepts/#image) from your Container Registry. 
+    - Select the required Container Registry namespace from the drop-down list, and then select the container and tag.
     - Choose the [port](/serverless/containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable.
     - Choose a **name** for your container and, optionally, a **description**. The name must only contain alphanumeric characters and dashes.
     - Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container.
         <Message type="note">
-        Available memory depends on allocated vCPU, and maximum ephemeral storage value depends on allocated memory.
+        Available memory depends on allocated vCPU, and the maximum ephemeral storage value depends on allocated memory.
         </Message>
     - Set your [scaling](/serverless/containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here.
     - Click **Advanced options** to define any [environment variables](/serverless/containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
-    - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables which are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
+    - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
         <Message type="note">
         Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
         </Message>
@@ -76,7 +77,7 @@ Private external container registries are currently not supported.
         </Message>
     - Set your [scaling](/serverless/containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here.
     - Click **Advanced options** to define any [environment variables](/serverless/containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
-    - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables which are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
+    - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
         <Message type="note">
         Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
         </Message>

serverless/jobs/how-to/create-job.mdx

@@ -14,7 +14,7 @@ categories:
   - jobs
 ---
 
-This page shows you how to create Serverless Jbs using the [Scaleway console](https://console.scaleway.com/).
+This page shows you how to create Serverless Jobs using the [Scaleway console](https://console.scaleway.com/).
 
 You can create a job from the [Scaleway Container Registry](/containers/container-registry/quickstart/), or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc.