Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>

Author: SamyOubouaziz

pages/serverless-containers/troubleshooting/cannot-access-container.mdx

@@ -30,10 +30,10 @@ I am experiencing issues while accessing my Serverless Containers.
 - If you encounter a DNS issue, refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/known-dns-containers-errors/).
 
 - For long response time, check:
-    - if the first instance of the container is currently starting, a [cold start](/serverless-containers/concepts/#cold-start) can appear
+    - if the first instance of the container is currently starting. This can entail a [cold start](/serverless-containers/concepts/#cold-start)
     - if not, [check the metrics in Cockpit](/serverless-containers/how-to/monitor-container/) (especially CPU) and see if there is a high usage explaining the slow response
 
-- `HTTP 5XX` errors can come from the application itself. Check if you can reproduce locally with a dummy container, or if your application is not misbehaving. 
+- `HTTP 5XX` errors can come from the application itself. Check if you can reproduce locally with a dummy container, or if your application is misbehaving. 
 
 - A `Could not resolve host` error can indicate that you are trying to reach the container in IPv4 with its IPv6 address, or vice versa. This can also appear if there is a [DNS issue](/serverless-containers/troubleshooting/known-dns-containers-errors/).
 

pages/serverless-containers/troubleshooting/known-dns-containers-errors.mdx

@@ -27,7 +27,7 @@ The DNS record for the default endpoint (`functions.fnc.<region>.scw.cloud`) is
 ## Solutions
 
 - When the DNS answer is cached locally, you can:
-  - retry later (negative DNS caching last around 60 seconds)
+  - retry later (negative DNS caching lasts around 60 seconds)
   - try from another host, where the DNS answer is not cached
   - clean the DNS cache locally
   - use another DNS resolver (common DNS resolvers should have the record in a few seconds)
@@ -42,4 +42,4 @@ The DNS record for the default endpoint (`functions.fnc.<region>.scw.cloud`) is
 
 - Refer to the dedicated documentation on [how to add a custom domain to a container](/serverless-containers/how-to/add-a-custom-domain-to-a-container/) for more information.
 
-- If you managed your domain names with Scaleway, refer to the [Scaleway Domains and DNS documentation](/domains-and-dns/).
+- If you manage your domain names with Scaleway, refer to the [Scaleway Domains and DNS documentation](/domains-and-dns/).