docs(srv): update

Author: SamyOubouaziz

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

@@ -41,7 +41,7 @@ You can deploy a container from the [Scaleway Container Registry](/container-reg
         Available memory depends on allocated vCPU, and the maximum ephemeral storage value depends on allocated memory.
         </Message>
 5. Set your [autoscaling](/serverless-containers/concepts/#autoscaling) preferences:
-    - **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent request received on each active instance of your container.
+    - **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent requests received on each active instance of your container.
     - **CPU percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the CPU load.
     - **RAM percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the RAM used.
 6. In the **Advanced options** section set the following:
@@ -95,10 +95,10 @@ Private external container registries are currently not supported.
     - 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>
 5. Set your [autoscaling](/serverless-containers/concepts/#autoscaling) preferences:
-    - **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent request received on each active instance of your container.
+    - **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent requests received on each active instance of your container.
     - **CPU percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the CPU load.
     - **RAM percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the RAM used.
 6. In the **Advanced options** section set the following: