Fix typos

Author: Moiman

src/content/11/en/part11e.md

@@ -19,7 +19,7 @@ A common use of this is to have some reference to the tracking system in Git pul
 
 When the CI process finishes quickly, it can be convenient to just watch it execute and wait for the result. As projects become more complex, so too does the process of building and testing the code. This can quickly lead to a situation where it takes long enough to generate the build result that a developer may want to begin working on another task. This in turn leads to a forgotten build. 
 
-This is especially problematic if we're talking about merging PRs that may affect another developer's work, either causing problems or delays for them. This can also lead to a situation where you think you've deployed something but haven't actually finished a deployment, this can lead to mis-communication with teammates and customers (e.g. "Go ahead and try that again, the bug should be fixed").
+This is especially problematic if we're talking about merging PRs that may affect another developer's work, either causing problems or delays for them. This can also lead to a situation where you think you've deployed something but haven't actually finished a deployment, this can lead to miscommunication with teammates and customers (e.g. "Go ahead and try that again, the bug should be fixed").
 
 There are several solutions to this problem ranging from simple notifications to more complicated processes that simply merge passing code if certain conditions are met. We're going to discuss notifications as a simple solution since it's the one that interferes with the team workflow the least.
 

src/content/3/en/part3d.md

@@ -133,7 +133,7 @@ It is also vital to follow continuously the server logs. The problem became obvi
 
 The database url was _undefined_, so the command *fly secrets set MONGODB\_URI* was forgotten.
 
-When using Render, the database url is given by definig the proper env in the dashboard:
+When using Render, the database url is given by defining the proper env in the dashboard:
 
 ![browser render showing the MONGODB_URI env variable](../../images/3/render-env.png)
 

src/content/8/en/part8b.md

@@ -233,7 +233,7 @@ The name of the query is <i>findPersonByName</i>, and it is given a string <i>$n
 
 It is also possible to do queries with parameters with the Apollo Explorer. The parameters are given in <i>Variables</i>:
 
-![apollostudio findPersonByName highlighting nameToSEarch Arto Hellas](../../images/8/10x.png)
+![apollostudio findPersonByName highlighting nameToSearch Arto Hellas](../../images/8/10x.png)
 
 The *useQuery* hook is well-suited for situations where the query is done when the component is rendered.  However, we now want to make the query only when a user wants to see the details of a specific person, so the query is done only [as required](https://www.apollographql.com/docs/react/data/queries/#executing-queries-manually).
 

src/content/9/en/part9d.md

@@ -376,7 +376,7 @@ Besides the attributes that are found in the various course parts, we have now i
 Next, we will create a type [union](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#union-types) of all these types. We can then use it to define a type for our array, which should accept any of these course part types:
 
 ```js
-type CoursePart = CoursePartBasic | CoursePartGroup | CoursePartBackround;
+type CoursePart = CoursePartBasic | CoursePartGroup | CoursePartBackground;
 ```
 
 Now we can set the type for our *courseParts* variable: