Applied review suggestions

Author: pablo-maff

src/content/12/en/part12a.md

@@ -34,7 +34,7 @@ You can probably use nvm, virtual machines, or dark magic to get them running at
 
 It is not uncommon that the application just does not run on the server despite it works just fine on your machine. It may be due to some missing dependency or other differences in the environments. Here containers are an excellent solution since you can run the application in the same execution environment both on your machine and on the server. It is not perfect: different hardware can be an issue, but you can limit the differences between environments.
 
-Sometimes you may hear about the <i>"Works in my container"</i> issue. The phrase describes a situation in which the application works fine in a container running on your machine but breaks when the container is started on a server. The phrase is a play on the infamous <i>"Works on my machine"</i> issue, which containers are often promised to solve. The situation also is most likely, an usage error.
+Sometimes you may hear about the <i>"Works in my container"</i> issue. The phrase describes a situation in which the application works fine in a container running on your machine but breaks when the container is started on a server. The phrase is a play on the infamous <i>"Works on my machine"</i> issue, which containers are often promised to solve. The situation also is most likely an usage error.
 
 ### About this part
 

src/content/12/en/part12b.md

@@ -500,7 +500,7 @@ Build it to an image with the command:
 docker build -t initialized-mongo .
 ```
 
-Change now the <i>docker-compose.dev.yml</i> file to use the new image:
+Now change the <i>docker-compose.dev.yml</i> file to use the new image:
 
 ```yml
   mongo:

src/content/12/en/part12c.md

@@ -154,7 +154,7 @@ COPY --from=build-stage /usr/src/app/dist /usr/share/nginx/html
 # highlight-end
 ```
 
-We have declared also <i>another stage</i>, to where only the relevant files of the first stage (the <i>dist</i> directory, that contains the static content) are copied.
+We have also declared <i>another stage</i>, where only the relevant files of the first stage (the <i>dist</i> directory, that contains the static content) are copied.
 
 After we build it again, the image is ready to serve the static content. The default port will be 80 for Nginx, so something like _-p 8000:80_ will work, so the parameters of the RUN command need to be changed a bit.