Merge pull request #2781 from Moiman/typo-fixes

Typo fixes

Author: mluukkai

src/content/0/en/part0a.md

@@ -63,7 +63,7 @@ A better question could be
 >
 > ```js
 >   // the relevant part of code is pasted here
->   // code should contain several console.log statements for helping the debuging
+>   // code should contain several console.log statements for helping the debugging
 > ```
 >
 > The following gets printed to the console

src/content/0/fi/osa0a.md

@@ -180,7 +180,7 @@ Koeaika on 120 minuuttia. Jos koesuoritus hyväksytään, saat seuraavan vahvist
 
 Jos et pääse kokeesta läpi, voit yrittää uudelleen viikon kuluttua.
 
-Jos pääset kokeesta läpi, ja et halua tehdä enempää tehtäviä, voit mennä palautussovelluksen my submissons -välilehdelle ja pyytää suorituksen rekisteröintiä:
+Jos pääset kokeesta läpi, ja et halua tehdä enempää tehtäviä, voit mennä palautussovelluksen my submissions -välilehdelle ja pyytää suorituksen rekisteröintiä:
 
 ![](../../images/0/enroll5a.png)
 

src/content/10/en/part10a.md

@@ -109,7 +109,7 @@ After you have set up the emulator and it is running, start the Expo development
 
 In addition to emulators, there is one extremely useful way to develop React Native applications with Expo, the Expo mobile app. With the Expo mobile app, you can preview your application using your actual mobile device, which provides a bit more concrete development experience compared to emulators. To get started, install the Expo mobile app by following the instructions in the [Expo's documentation](https://docs.expo.io/get-started/installation/#2-expo-go-app-for-ios-and). Note that the Expo mobile app can only open your application if your mobile device is connected to <i>the same local network</i> (e.g. connected to the same Wi-Fi network) as the computer you are using for development.
 
-When the Expo mobile app has finished installing, open it up. Next, if the Expo development tools are not already running, start them by running <em>npm start</em>. You should be able to see a QR code at the beginning of the command output. Open the app by scanning the QR code, in Anroid with Expo app or in iOS with the Camera app.
+When the Expo mobile app has finished installing, open it up. Next, if the Expo development tools are not already running, start them by running <em>npm start</em>. You should be able to see a QR code at the beginning of the command output. Open the app by scanning the QR code, in Android with Expo app or in iOS with the Camera app.
 The Expo mobile app should start building the JavaScript bundle and after it is finished you should be able to see your application. Now, every time you want to reopen your application in the Expo mobile app, you should be able to access the application without scanning the QR code by pressing it in the <i>Recently opened</i> list in the <i>Projects</i> view.
 
 </div>

src/content/11/en/part11c.md

@@ -248,7 +248,7 @@ v11    	true  	release 	succeeded	Deploy image           	[email protected]	59m25s
 v10    	true  	release 	succeeded	Deploy image           	[email protected]	1h6m ago
 ```
 
-So despite the problems in the relese, the app stays functional!
+So despite the problems in the release, the app stays functional!
 
 Before moving to next exercise, fix your deployment and ensure that the application works again as intended.
 
@@ -293,7 +293,7 @@ Now when you know that the script based health check works, it is time to define
 
 <i>Write a script ensuring the health check endpoint (that is, the GET request to '/health') not only works, but also returns the correct string 'ok'.</i>
 
-You propably should use [curl](https://curl.se/) in the script to do the HTTP request. You most likely need to Google how to get hold to the returned string and compare it with the expected value 'ok'.
+You probably should use [curl](https://curl.se/) in the script to do the HTTP request. You most likely need to Google how to get hold to the returned string and compare it with the expected value 'ok'.
 
 By default _curl_ does not exist in the Fly.io virtual machine. You can install it by adding the following line in the file _Dockerfile_ that gets created in your project root directory when Fly.io app is set up:
 
@@ -316,7 +316,7 @@ ENV PATH /root/.volta/bin:$PATH
 CMD [ "npm", "run", "start" ]
 ```
 
-It is <strong>strongly advisable</strong> to check first locally that the script works since so many things can go wrong in it, and when run in GitHub Action, you can not do any debug printing. If and <i> when</i> things do not work as indended, it is also a very good idea to log in to the virtual machine (with <i>flyctl ssh console</i>) and check that the script works when ran manually there.
+It is <strong>strongly advisable</strong> to check first locally that the script works since so many things can go wrong in it, and when run in GitHub Action, you can not do any debug printing. If and <i> when</i> things do not work as intended, it is also a very good idea to log in to the virtual machine (with <i>flyctl ssh console</i>) and check that the script works when ran manually there.
 
 *Note* that in order to test the script in the virtual machine, you should have the script in your local directory when you make a successful deployment. So if your deployment fails, the script will not be uploaded to the Fly.io server. So in case of problems, comment out the script based health check from fly.toml and do a deployment to get your script to the virtual machine.
 
@@ -355,7 +355,7 @@ $ ./build_step.sh
 Build script
 ```
 
-You also need to open the <i>Advanced settings</i> and turn the auto-deploy off since we want to controll the deployment in the GitHub Actions:
+You also need to open the <i>Advanced settings</i> and turn the auto-deploy off since we want to control the deployment in the GitHub Actions:
 
 ![](../../images/11/render2.png)
 

src/content/11/en/part11d.md

@@ -233,7 +233,7 @@ By clicking <i>view all tags</i>, you can see all the tags listed:
 
 ![Releases](../../images/11/18-new.png)
 
-And if needed, you can navigate to the view of a single tag that shows eg. what is the GitHub commit corressponding to the tag.
+And if needed, you can navigate to the view of a single tag that shows eg. what is the GitHub commit corresponding to the tag.
 
 #### 11.16 Skipping a commit for tagging and deployment
 

src/content/11/en/part11e.md

@@ -93,7 +93,7 @@ Use now the action [url-health-check](https://github.com/marketplace/actions/url
 
 **Note** that unfortunately it takes quite long until GitHub Actions starts the scheduled workflow for the first time. For me, it took nearly one hour. So it might be a good idea to get the check working firstly by triggering the workflow with Git push. When you are sure that the check is properly working, then switch to a scheduled trigger.
 
-**Note also** that once you get this working, it is best to drop the ping frequency (to max once in 24 hours) or disable the rule altogether since otherways your health check may consume all your monthly free hours.
+**Note also** that once you get this working, it is best to drop the ping frequency (to max once in 24 hours) or disable the rule altogether since otherwise your health check may consume all your monthly free hours.
 
 #### 11.20 Your own pipeline
 

src/content/12/en/part12c.md

@@ -627,14 +627,14 @@ Next, the browser starts executing the React app, and all the requests it makes
 
 ![](../../images/12/nginx-setup2.png)
 
-The frontent container is actually no more accessed beyond the first request that gets the React app source code to the browser.
+The frontend container is actually no more accessed beyond the first request that gets the React app source code to the browser.
 
 Set up now your app to work as in the abovefigure. Make sure that the todo-frontend works with todo-backend. It will require changes to the *REACT\_APP\_BACKEND\_URL* environmental variable in the frontend.
 
 Make sure that the development environment is now fully functional, that is:
 - all features of the todo app work
 - you can edit the source files <i>and</i> the changes take effect by reloading the app (the hot reloading may or may not work...)
-- frontend should access the backend throught Nginx, so the requests should be done to http://localhost:8080/api/todos:
+- frontend should access the backend through Nginx, so the requests should be done to http://localhost:8080/api/todos:
 
 ![](../../images/12/todos-dev-right-2.png)
 

src/content/2/en/part2e.md

@@ -498,7 +498,7 @@ const App = () => {
 
 The user interface of the application has a form, in the input field of which the name of the desired currency is written. If the currency exists, the application renders the exchange rates of the currency to other currencies:
 
-![browser showing currency exchange rates with eur typed and cosole saying fetching exchange rates](../../images/2/32new.png)
+![browser showing currency exchange rates with eur typed and console saying fetching exchange rates](../../images/2/32new.png)
 
 The application sets the name of the currency entered to the form to the state _currency_ at the moment the button is pressed.
 

src/content/3/en/part3a.md

@@ -868,7 +868,7 @@ Data:
 
 Output in the browser after GET request:
 
-![JSON data of 4 poeple in browser from api/persons](../../images/3/22e.png)
+![JSON data of 4 people in browser from api/persons](../../images/3/22e.png)
 
 Notice that the forward slash in the route <i>api/persons</i> is not a special character, and is just like any other character in the string.
 

src/content/3/en/part3b.md

@@ -399,7 +399,7 @@ Note that the directory paths in the script <i>build:ui</i> depend on the locati
 
 #### Render
 
-Note: When you attempt to deploy your backend to Render, make sure you have a seperate repository for the backend and deploy that github repo through Render, attempting to deploy through your Fullstackopen repository will often throw "ERR path ....package.json". 
+Note: When you attempt to deploy your backend to Render, make sure you have a separate repository for the backend and deploy that github repo through Render, attempting to deploy through your Fullstackopen repository will often throw "ERR path ....package.json".
 
 In case of Render, the scripts look like the following