diff --git a/book/installation-and-setup/user_types.md b/book/installation-and-setup/user_types.md
index 3fa687d..bd4b6e0 100644
--- a/book/installation-and-setup/user_types.md
+++ b/book/installation-and-setup/user_types.md
@@ -11,6 +11,15 @@ Different types of users will interact with the website or the Jupyter Books dif
3. **Colleague making adjustments to single files in GitLab/GitHub using single text editor**.
This type of user requires only very basic knowledge in GitLab/GitHub in order to make changes to the website themselves without needing to install any software! Making adjustments using single text editor only requires the user to be able to login into GitLab/GitHub and edit .md or .ipynb files. The changes can be done directly in the main or publish branch and if a new branch is needed for the changes then the set-up and merging can be taken care of by someone more familiar in GitLab/GitHub.
+```{Note}
+
+At this point, you might already be trying to see which user type fits you the best. We are aware that the lines between user types can be a bit blurry, especially between type 3, 4 and 5. For this reason, we would like to introduce a cool feature that we discovered.
+
+So in case you are (1) a user type 3 and want to dabble in git or (2) a user type 4/5 and want to make some quick edits with only a few clicks, then [this is a cool feature](/book/workflows/edit_book.md) that might come in handy later.
+
+For now, just carry on with getting started.
+```
+
4. **Colleague making text adjustments to multiple files at the same time locally**.
User 4 is a hybrid between type 3 and 5. Basically this user is making changes by editing the .md files locally using, for example, VS Code. Therefore, this user requires a little bit more knowledge on git (think of pulling and pushing changes) but their main focus remains to make adjustments to the content of the book by editing .md files whereas user type 5 has more knowledge to make changes to python files the book as well. This user can build the book online.
diff --git a/book/workflows/edit_book.md b/book/workflows/edit_book.md
index 0858182..d1d4168 100644
--- a/book/workflows/edit_book.md
+++ b/book/workflows/edit_book.md
@@ -610,4 +610,44 @@ Alternatively, you can also click on `Push origin` in the top bar.
``````
```````
````````
-`````````
\ No newline at end of file
+`````````
+
+## Additional Info - Quick Fixes - use VS Code in your Browser
+
+You might remember that when we introduced the [user types](/book/installation-and-setup/user_types.md), we quickly mentioned a cool feature for user type 3 wanting to get to know git and for user types 4 & 5 wanting to make a quick edit in the book with only a few clicks.
+
+Using this feature, you can open VS Code in your browser and edit the files in your repository. By doing this, you completely by-pass the need to open (and install) VS Code and GitHub Desktop on your laptop making it the optimal way to quickly fix something.
+
+1. Navigate to your repository in GitHub
+2. Press the dot key on your keyboard `.` This will open VS Code
+3. Navigate to a file and make some changes
+
+```{figure} ./figures/Online_VS1.PNG
+:name: VS Code in Browser
+:width: 70%
+:align: center
+
+VS Code in Browser
+```
+In the bottom left you can see the branch you are working in.
+
+4. This feature requires you to use git in VS Code. You can do that in the Source Control tab in the activity bar on the left side of the window (it looks like a branching icon). Write your commit message and click on commit & push.
+5. Now let's see the result. Go back to your GitHub repo. In the top bar, go to actions.
+
+```{figure} ./figures/Online_VS2.PNG
+:name: GitHub Actions
+:width: 70%
+:align: center
+
+GitHub Actions
+```
+You will see the latest commit you just did (in this case text). After the pipeline has run, the yellow icon will turn green. Click on the commit and scroll until you see the title Deployed Branches.
+
+```{figure} ./figures/Online_VS3.PNG
+:name: Deployed Branches
+:width: 60%
+:align: center
+
+Deployed Branches
+```
+Click on the link and admire your changes:)
\ No newline at end of file
diff --git a/book/workflows/figures/Online_VS1.PNG b/book/workflows/figures/Online_VS1.PNG
new file mode 100644
index 0000000..0899e26
Binary files /dev/null and b/book/workflows/figures/Online_VS1.PNG differ
diff --git a/book/workflows/figures/Online_VS2.PNG b/book/workflows/figures/Online_VS2.PNG
new file mode 100644
index 0000000..92e7482
Binary files /dev/null and b/book/workflows/figures/Online_VS2.PNG differ
diff --git a/book/workflows/figures/Online_VS3.PNG b/book/workflows/figures/Online_VS3.PNG
new file mode 100644
index 0000000..cca4930
Binary files /dev/null and b/book/workflows/figures/Online_VS3.PNG differ