Apply suggestions from code review

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

Author: thomas-tacquet

serverless/containers/concepts.mdx

@@ -166,11 +166,11 @@ Use cases:
 When deploying a new version of a Serverless Container, a rolling update is applied by default. This means that the new version of the service is gradually rolled out to your users without downtime.
 Here is how it works:
 
-* When a new version of your container is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed.
+* When a new version of your container is deployed, the platform automatically starts routing traffic to it incrementally, while still serving requests from the old version until the new one is fully deployed.
 * Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
 * The old version is decommissioned once the new version is fully serving traffic.
 
-This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it
+This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it.
 
 ## Sandbox