Merge pull request #3592 from guymelef/patch-6

edit phrasing + fix typo

src/content/11/en/part11c.md

@@ -19,7 +19,7 @@ Next, we're going to look at the principles of making a deployment safely and so
 
 We'd like to define some rules about how our deployment process should work but before that, we have to look at some constraints of reality.
 
-One on the phrasing of Murphy's Law holds that:
+One phrasing of Murphy's Law holds that:
  "Anything that can go wrong will go wrong."
 
 It's important to remember this when we plan out our deployment system. Some of the things we'll need to consider could include:
@@ -52,7 +52,7 @@ Let's define some things we **want** in this hypothetical deployment system too:
  - We would like it to be fast
  - We'd like to have no downtime during the deployment (this is distinct from the requirement we have for handling user requests just before/during the deployment).
 
-Next we will have three sets of exercises for automazing the deployment with GitHub Actions, one for [Fly.io](https://fly.io/), another one for [Render](https://render.com/). The process of deployment is always specific to the particular cloud provider, so you can also do both the exercise sets if you want to see the differences how these services work with respect to deployments.
+Next we will have three sets of exercises for automating the deployment with GitHub Actions, one for [Fly.io](https://fly.io/), another one for [Render](https://render.com/). The process of deployment is always specific to the particular cloud provider, so you can also do both the exercise sets if you want to see the differences how these services work with respect to deployments.
 
 ### Has the app been deployed?