Merge branch 'fullstack-hy2020:source' into brazilian-portuguese-translation

Author: CassivsGabriellis

src/content/3/en/part3b.md

@@ -399,6 +399,8 @@ 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". 
+
 In case of Render, the scripts look like the following
 
 ```json

src/content/4/en/part4b.md

@@ -1006,7 +1006,7 @@ Full stack development is <i> extremely hard</i>, that is why I will use all the
 - <i>I will write lots of _console.log_ statements to make sure I understand how the code and the tests behave and to help pinpoint problems</i>
 - If my code does not work, I will not write more code. Instead, I start deleting the code until it works or just return to a state when everything was still working
 - <i>If a test does not pass, I make sure that the tested functionality for sure works in the application</i>
-- When I ask for help in the course Discord or Telegram channel or elsewhere I formulate my questions properly, see [here](https://fullstackopen.com/en/part0/general_info#how-to-ask-help-in-discord-telegam) how to ask for help
+- When I ask for help in the course Discord or Telegram channel or elsewhere I formulate my questions properly, see [here](https://fullstackopen.com/en/part0/general_info#how-to-get-help-in-discord-telegram) how to ask for help
 
 </div>
 

src/content/6/en/part6d.md

@@ -770,7 +770,7 @@ The notification is displayed for five seconds.
 
 #### Exercise 6.24.
 
-As stated in exercise 6.20, the server requires that the content of the anecdote to be added is at least 5 characters long. Now implement error handling for the insertion. In practice, it is sufficient to display a notification to the user in case of a failed POST request:
+As stated in exercise 6.21, the server requires that the content of the anecdote to be added is at least 5 characters long. Now implement error handling for the insertion. In practice, it is sufficient to display a notification to the user in case of a failed POST request:
 
 ![browser showing error notification for trying to add too short of an anecdoate](../../images/6/67new.png)
 

src/content/8/en/part8c.md

@@ -346,7 +346,7 @@ In the Apollo Explorer, the header is added to a query like so:
 
 ![apollo explorer highlighting headers with authorization and bearer token](../../images/8/24x.png)
 
-Modify the startup of the backend by giving the function that handles the startup [startStandaloneServer](https://www.apollographql.com/docs/apollo-server/api/standalone/) another parameter [context](https://www.apollographql.com /docs/apollo-server/data/context/)
+Modify the startup of the backend by giving the function that handles the startup [startStandaloneServer](https://www.apollographql.com/docs/apollo-server/api/standalone/) another parameter [context](https://www.apollographql.com/docs/apollo-server/data/context/)
 
 ```js
 startStandaloneServer(server, {
@@ -564,7 +564,7 @@ Add user management to your application. Expand the schema like so:
 ```js
 type User {
   username: String!
-  favouriteGenre: String!
+  favoriteGenre: String!
   id: ID!
 }
 
@@ -581,7 +581,7 @@ type Mutation {
   // ...
   createUser(
     username: String!
-    favouriteGenre: String!
+    favoriteGenre: String!
   ): User
   login(
     username: String!

src/content/8/en/part8d.md

@@ -189,7 +189,7 @@ const client = new ApolloClient({
 })
 ```
 
-The field *uri* that was previously used when creating the *client* object has been replaced by the field *link*, which defines in a more complicated case how Apollo is connected to the server. The server url is now wrapped using the function [createHttpLink](https://www.apollographql.com/docs/link/links/http.htm) into a suitable httpLink object. The link is modified by the [context](https://www .apollographql.com/docs/react/api/link/apollo-link-context/#overview) defined by the authLink object so that a possible token in localStorage is [set to header](https://www.apollographql.com/docs/react/networking/authentication /#header) <i>authorization</i> for each request to the server.
+The field *uri* that was previously used when creating the *client* object has been replaced by the field *link*, which defines in a more complicated case how Apollo is connected to the server. The server url is now wrapped using the function [createHttpLink](https://www.apollographql.com/docs/link/links/http.htm) into a suitable httpLink object. The link is modified by the [context](https://www.apollographql.com/docs/react/api/link/apollo-link-context/#overview) defined by the authLink object so that a possible token in localStorage is [set to header](https://www.apollographql.com/docs/react/networking/authentication/#header) <i>authorization</i> for each request to the server.
 
 Creating new persons and changing numbers works again. There is however one remaining problem. If we try to add a person without a phone number, it is not possible.