docs: formatting

Author: Kian Khoshnoodpour

internals/wiki/00-development-environment.md

@@ -9,4 +9,4 @@ The development environment described here is the most commonly used one and the
 1. Run `yarn` from the root folder of the cloned folder
 1. Open the cloned folder using VSCode
 
-Now we're all set to use GraphQL!
+Now we're all set!

internals/wiki/01-my-first-query.md

@@ -1,6 +1,7 @@
 # Chapter 1: My first query
 
-> [Frontend, Backend]
+> [Frontend, Backend] 
+> Continues from branch `master`
 
 In this assignment we're going to add a new query that we can use in our application. We do this by:
 

internals/wiki/02-calling-graphql-from-react.md

@@ -1,6 +1,7 @@
 # Chapter 2 - Calling GraphQL from React
 
-> [Frontend]
+> [Frontend] 
+> Continues from branch `chapter-1-solution`
 
 In this chapter we'll use the GraphQL query we defined in chapter 1 and display it in our React application.
 

internals/wiki/03-server-side-rendering.md

@@ -1,6 +1,7 @@
 # Chapter 3: Server Side Rendering
 
-> [Frontend]
+> [Frontend] 
+> Continues from branch `chapter-2-solution`
 
 In the previous chapter we connected to GraphQL and showed the data in our application. What might not be obvious, is that we're performing the query server-side. The component is rendered on the server and the entire HTML including our component is returned.
 

internals/wiki/04-covid-app.md

@@ -1,6 +1,6 @@
 ## Chapter 4: Project - COVID app
 
-> [Backend, Frontend]
+> [Backend, Frontend] 
 > Continue from branch `master`
 
 In this chapter we're going to use what we learned so far to build a covid app.

internals/wiki/05-paging.md

@@ -1,8 +1,7 @@
 # Chapter 5: Paging
 
-> [Frontend, Backend]
-
-Resume from `chapter-3-solutions`
+> [Frontend, Backend] 
+> Continues from `chapter-3-solutions`
 
 In this chapter we add paging to our query. There are many ways to implement paging in an API. The most common ones are to either use a `page` or an `offset`. Or if you're really cool, you'll use a `cursor`. The following section explains the first two paging schemes. If you already know how to implement paging in API's, you can skip this section and start at the first assignment of the chapter.
 

internals/wiki/06-lazy-queries.md

@@ -1,6 +1,7 @@
 ## Chapter 6: Lazy queries
 
-> [Frontend]
+> [Frontend] 
+> Continues from `chapter-5-solution`
 
 In the previous chapters we used query hooks to get our data from GraphQL. In all our cases we retrieved the data immediatly on page load.
 

internals/wiki/07-mutations.md

@@ -1,6 +1,7 @@
 # Chapter 7: Mutations
 
-> [Frontend, Backend]
+> [Frontend, Backend] 
+> Continues from `chapter-6-solution`
 
 So far we've learned how to display data from our GraphQL API. In this chapter we're going to learn how to change or update our data using GraphQL.
 

internals/wiki/08-fragments.md

@@ -1,7 +1,6 @@
 # Chapter 8: Fragments
 
-> [Frontend]
-
+> [Frontend] 
 > Continues from branch `chapter-7-solution`
 
 A common best practice is to split React components into separate stateless and stateful components, also referred to as dumb and smart components. So far we've been building stateful components: The component handles both data fetching as well as styling. There are a few ways we can split our components while still using the GraphQL type system.

internals/wiki/09-union-types.md

@@ -1,7 +1,6 @@
 # Chapter 9: Union Types
 
-> [Frontend, Backend]
-
+> [Frontend, Backend] 
 > Continues from branch `chapter-8-solution`
 
 In this chapter we will go through the use cases for `unions` and how to implement them in our GraphQL schema. The Union type indicates that a field can return more than one object type, but doesn't define specific fields itself.