diff --git a/book/workflows/edit_book.md b/book/workflows/edit_book.md
index 75c6363..7be8715 100644
--- a/book/workflows/edit_book.md
+++ b/book/workflows/edit_book.md
@@ -161,34 +161,96 @@ Alternatively, you can also click on `Push origin` in the top bar.
``````{tab-item} ... an existing version (branch)...
-**... by (1) regularly obtaining updates from colleagues from GitLab/GitHub (pulling),
- (2) solving potential incompatible changes (merging conflicts),
- (3) making changes on a single / multiple file(s),
- (4) selecting changes to be added to the Git-timeline (staging),
- (5) adding those to the Git-timeline (committing) and
+**... by (1) regularly obtaining updates from colleagues from GitLab/GitHub (pulling),
+ (2) solving potential incompatible changes (merging conflicts),
+ (3) making changes on a single / multiple file(s),
+ (4) selecting changes to be added to the Git-timeline (staging),
+ (5) adding those to the Git-timeline (committing) and
(6) adding changes to GitLab/GitHub (pushing) with ...**
`````{tab-set}
````{tab-item} ... Git in VS Code
-**Eventually solve conflicts with combining versions (merge conflicts, emerges after pulling)**
+1. If you collaborate with colleagues on your branch, you can get the updates from your colleagues as well by pulling from GitLab/GitHub. This synchronizes the remote repositery with your local repositery on your machine. On the left side-bar click on the icon that looks like a branch.
-If you collaborate with colleagues on this branch, you can get the updates from your colleagues as well by pulling from GitLab/GitHub. Now your branch is up-to-date. However, this might lead into a merge conflict if you and colleagues have made incompatible changes. How to solve that?
+
+
+
-```{error} To be written
+By clicking on the 🔄 button, you will pull your colleages' changes.
+
+2. When multiple people work on one chapter, it is possible that conflicts will arise if you and your colleagues have made incompatible changes in the same branch. In that case, when pulling from the remote repositery, Git in VS Code will recognize conflicts and help you to solve potential incompatible changes (merging conflicts). Open the files that are marked as conflicitng.
+
+
+
+
+
+The figure above shows the conflicts. If you look closely you can see that the last couple of words of the paragraph are different in the main branch than in the branch we were working in. There are a couple of options in the top bar:
+
+- `Accept Current Change` will keep the change in your branch
+- `Accept Incoming Change` will keep the change from the main branch (the branch you are merging into your branch)
+- `Accept Both Changes` will retain both paragraphs
+
+Choose one of the options to resolve the merge conflict. You now have updated your work with work from your colleagues and resolved potential conlicts. You are now ready to continue working on the content.
+
+3. Make some further changes to a file in for example VS Code and save them.
+
+4. Select the files ready to be added to Git-timeline (staging)
+
+For demonstration purposes, we have created a new Markdown file called `new-chapter.md`, which we want to add to the book. Since this is a new file, Git has no knowledge about its existence yet. I.e., the file is *untracked*. To add new files to our repository, we need to *stage* and *commit* them. To do this, open the Source Control menu in the left side bar. Our new file should appear in this menu:
+
+```{figure} ../images/git-new-file.png
+
+The new file appears in the Source Control menu.
```
+
+Notice that there is a green letter U placed besides the file, meaning that our file is untracked. To add a file to the *staging area*, click on the + that appears when you hover over the file.
+
+5. Adding changes to the Git-timeline (committing)
+
+Next, in the field that says "Message", write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, the menu should now look something like this:
+
+```{figure} ../images/git-file-added.png
+
+The new file has been staged, and we've written a Commit Message.
+```
+Now, we are ready to add the changes to the repository. This is done by *committing* the staged changes. To do this, simply press the big, blue "Commit" button in the Source Control menu.
+
+In the bottom left corner, next to the branch name, click the "Synchronize Changes" button (the one that looks like this: 🔄, highlighted in the image below) to push the changes to GitLab.
+
+```{figure} ../images/git-push.png
+
+After committing, click the 🔄 button to push our changes to the remote repository.
````
````{tab-item} ... GitHub Desktop
-1. Obtain updates from colleagues from GitLab/GitHub (pulling). This synchronizes the remote repositery with your local repositery on your machine. Click on `Fetch` in the top bar. Then on the same place, click on 'Pull'.
+1. If you collaborate with colleagues on your branch, you can get the updates from your colleagues as well by pulling from GitLab/GitHub. This synchronizes the remote repositery with your local repositery on your machine. Click on `Fetch` in the top bar. Then on the same place, click on 'Pull'.
-2. When multiple people work on one chapter, it is possible that conflicts will arise. This means that two users might have cheanged the same sections. GitHub Desktop will recognize this Solve potential incompatible changes (merging conflicts)
+2. When multiple people work on one chapter, it is possible that conflicts will arise if you and your colleagues have made incompatible changes in the same branch. In that case, when pulling from the remote repositery, GitHub Desktop will recognize conflicts and help you to solve potential incompatible changes (merging conflicts).
-3. Make some changes to a file in for example VS Code and save them.
+
+
+
+
+In this case there are two conflicted files. GitHub Desktop is suggesting to resolve the changes in VS Code. Click on `Open in Visual Studio Code`.
+
+
+
+
+
+The figure above shows the conflicts. If you look closely you can see that the last couple of words of the paragraph are different in the main branch than in the branch we were working in. There are a couple of options in the top bar:
+
+- `Accept Current Change` will keep the change in your branch
+- `Accept Incoming Change` will keep the change from the main branch (the branch you are merging into your branch)
+- `Accept Both Changes` will retain both paragraphs
+
+Choose one of the options to resolve the merge conflict. You now have updated your work with work from your colleagues and resolved potential conlicts. You are now ready to continue working on the content.
+
+3. Make some further changes to a file in for example VS Code and save them.
4. The staging GitHub Desktop assumes you want to stage all files. These files will show up on the left side bar when you open GitHub Desktop. You can unselect some of them (unstaging them) by clicking on the *check*.
@@ -216,25 +278,51 @@ Alternatively, you can also click on `Push origin` in the top bar.
```````
````````
-````````{tab-item} User type 5
+````````{tab-item} ... User type 5 ...
```````{tab-set}
``````{tab-item} ... brand new version (branch)
-(**... by making changes on a single / multiple file(s), checking changes locally, selecting changes to be added to the Git-timeline (staging), adding those to the Git-timeline (committing) and adding those changes to GitLab/GitHub (pushing) with ...**)
-
**... by (1) making changes on a single or multiple file(s)
- (2) checking changes locally,
- (2) selecting changes to be added to the Git-timeline (staging)
- (3) adding changes to the Git-timeline (committing) and
- (4) adding changes to GitLab/GitHub (pushing) with ...**
+ (2) checking changes locally,
+ (3) selecting changes to be added to the Git-timeline (staging)
+ (4) adding changes to the Git-timeline (committing) and
+ (5) adding changes to GitLab/GitHub (pushing) with ...**
`````{tab-set}
````{tab-item} ... Git in VS Code
1. Make some changes to a file in for example VS Code and save them.
-2. Select the files ready to be added to Git-timeline (staging)
+2. Once all the changes are made, it can be useful to check the changes locally on your device in order to see how it will look on the website. If all the required environments and packages are downloaded, checking changes locally is fairly easy!
+
+Navigate to the terminal in VS code, located at the bottom of the window or by clicking on `Terminal` in the top bar.
+You will firstly need to actiavte the right environment. Type the following command:
+
+`conda activate jupyter-book-env`
+
+(or the environment in which you have installed the TeachBooks package)
+
+Then we can build the book locally. Make sure you are in the right repositery in VS code and type the folloing command:
+
+`jupyter-book build book`
+
+Where book is the name of the folder containing all the files that make up your book. After `jupyter-book` is done running you will get the following:
+
+```{figure} ../figures/buildbook.PNG
+
+Output.
+```
+Paste the last line into your browser to see the updated changes.
+
+```{Note}
+
+Sometimes there are problems building the book. It could be that the building requires extensions that are not present in your environment. To prevent issues, make sure to update your environment by routinely updating your packages. You can do this by executing the following line in your environment in the command line.
+
+`pip install -r requirements.txt --upgrade`
+
+```jup
+3. If you are satisfied with your changes, you can select the files ready to be added to Git-timeline (staging)
For demonstration purposes, we have created a new Markdown file called `new-chapter.md`, which we want to add to the book. Since this is a new file, Git has no knowledge about its existence yet. I.e., the file is *untracked*. To add new files to our repository, we need to *stage* and *commit* them. To do this, open the Source Control menu in the left side bar. Our new file should appear in this menu:
@@ -245,7 +333,7 @@ The new file appears in the Source Control menu.
Notice that there is a green letter U placed besides the file, meaning that our file is untracked. To add a file to the *staging area*, click on the + that appears when you hover over the file.
-3. Adding changes to the Git-timeline (committing)
+4. Adding changes to the Git-timeline (committing)
Next, in the field that says "Message", write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, the menu should now look something like this:
@@ -261,10 +349,10 @@ In the bottom left corner, next to the branch name, click the "Synchronize Chang
After committing, click the 🔄 button to push our changes to the remote repository.
-4. build book locally and eventually startup python server...
+```{Error}
+
+5. startup python server...
-```{error} To be written
-```
````
````{tab-item} ... GitHub Desktop
@@ -307,7 +395,13 @@ Python stuff?
``````{tab-item} ... existing version (branch)
-**... by regularly obtaining updates from colleagues from GitLab/GitHub (pulling), solving potential incompatible changes (merge conflicts), making changes on a single / multiple file(s), checking changes locally, selecting changes to be added to the Git-timeline (staging), adding those to the Git-timeline (committing) and adding those changes to GitLab/GitHub (pushing) with ...**
+**... by (1) regularly obtaining updates from colleagues from GitLab/GitHub (pulling),
+ (2) solving potential incompatible changes (merging conflicts),
+ (3) making changes on a single / multiple file(s),
+ (4) checking changes locally,
+ (5) selecting changes to be added to the Git-timeline (staging),
+ (6) adding those to the Git-timeline (committing) and
+ (7) adding changes to GitLab/GitHub (pushing) with ...**
`````{tab-set}
````{tab-item} ... Git in VS Code
diff --git a/book/workflows/figures/Conflicts1.PNG b/book/workflows/figures/Conflicts1.PNG
new file mode 100644
index 0000000..fcf7be3
Binary files /dev/null and b/book/workflows/figures/Conflicts1.PNG differ
diff --git a/book/workflows/figures/Conflicts2.PNG b/book/workflows/figures/Conflicts2.PNG
new file mode 100644
index 0000000..b33946c
Binary files /dev/null and b/book/workflows/figures/Conflicts2.PNG differ
diff --git a/book/workflows/figures/VSCode_Pull.PNG b/book/workflows/figures/VSCode_Pull.PNG
new file mode 100644
index 0000000..b65ed03
Binary files /dev/null and b/book/workflows/figures/VSCode_Pull.PNG differ
diff --git a/book/workflows/figures/buildbook.PNG b/book/workflows/figures/buildbook.PNG
new file mode 100644
index 0000000..7d62d7a
Binary files /dev/null and b/book/workflows/figures/buildbook.PNG differ
+
+
+