diff --git a/external/contribute/markdown/markdown.md b/external/contribute/markdown/markdown.md
index bebe01d6082114e6f07902cc507f1473c53071ab..c2c2960fd9d5c7ca72ff11f296e390638a078750 100644
--- a/external/contribute/markdown/markdown.md
+++ b/external/contribute/markdown/markdown.md
@@ -10,7 +10,7 @@ redirect_from:
 ---
 # Markdown
 
-Markdown is a lightweight markup language with plain text formatting syntax which became very popular in past decade and which nowadays serves as a standard in various digital communication channels.
+[Markdown](https://daringfireball.net/projects/markdown/) is a lightweight markup language with plain text formatting syntax which became very popular in past decade and which nowadays serves as a standard in various digital communication channels.
 
 ## Main features of Markdown
 
@@ -22,15 +22,16 @@ Markdown is a lightweight markup language with plain text formatting syntax whic
 * It is portable - since it is actually plain text, it can be opened by literally all text editors.
 * It is machine readable - as simple text, markdown documents can be tracked and version using a versioning system (Git, SVN)
 * It has small file size.
-* It is easy to convert to other formats - existing editors and command line tools (e.g. [pandoc](https://pandoc.org/) allows for easy conversion between Markdown and other widely used formats like HTML, PDF, docx, LaTeX, etc.
+* It is easy to convert to other formats - existing editors and command line tools (e.g. [Pandoc](https://pandoc.org/) allows for easy conversion between Markdown and other widely used formats like HTML, PDF, docx, LaTeX, etc.
 
 ## Quick reference
 
 * The following symbol <img src="img/visual-code_img_9.png" height="20"> behind the file name means that your changes/writing is not saved. Press CTRL+S to save your procedure
 * To preview your writing click on:
+
   <img src="img/visual-code_img_10.png">
 
-## Tips to write in markdown:
+## Tips to write in Markdown:
 
 | Markdown                           | Rendered Output           |
 |:-----------------------------------|---------------------------|
@@ -61,7 +62,7 @@ Markdown is a lightweight markup language with plain text formatting syntax whic
 |:-----------------------------------|---------------------------|
 |: Include links referring to a web `[page](https://www.markdownguide.org/)`. Avoid links in format `<link>` as it is not always parsed correctly. | Include links referring to a web [page](https://www.markdownguide.org/). Avoid links in format <link> as it is not always parsed correctly (like in this case).
 |:-----------------------------------|---------------------------|
-|: Include local pictures using markdown |
+|: Include local pictures using Markdown |
 |: ^^<pre>![My awesome picture](img/r3_logo.png)</pre> | ^^ ![My awesome picture](img/r3_logo.png)
 |: Or use HTML tag allowing you to alter the image properties (e.g. size) |
 |: ^^<pre>&lt; img src="img/r3_logo.png" width="40" &gt;</pre> | ^^<img src="img/r3_logo.png" width="40">
@@ -83,10 +84,10 @@ Plain syntax is usually enough. But special requirements lead to development of
 
 Another big advantage of Markdown is that it can contain HTML tags, which makes formatting very flexible.
 
-## When to use markdown?
+## When to use Markdown?
 
 * **Documentation** - Markdown is a perfect solution for description of a data package, project folder, workflow or code repository. Using Markdown ensures that the description will be accessible to everyone even after decades while still nicely structured. Guide for writing a good README is not covered by this HowTo page but you can find plenty of resources online, e.g.:
-  * [guide](https://data.research.cornell.edu/content/readme) from Cornell University, UK
+  * [Guide](https://data.research.cornell.edu/content/readme) from Cornell University, UK
   * [GitHub page](https://github.com/mhucka/readmine) for READMEs in a software repository
 * **Blogging and tutorials** - structured document with chunks of code, pictures and results of the analyses can be easily converted to HTML format and posted on personal/team websites.
 * **Notes and meeting minutes** - you can use following template for simple and nicely structured meeting notes:
diff --git a/external/contribute/mirror-fork/mirror-fork.md b/external/contribute/mirror-fork/mirror-fork.md
index 3c2f6e139b2a20c0bf4984dc13ded7a041026f5b..3b17e4050463057a85173791a348d38f60179216 100644
--- a/external/contribute/mirror-fork/mirror-fork.md
+++ b/external/contribute/mirror-fork/mirror-fork.md
@@ -17,7 +17,7 @@ you should follow the follow simple steps.
 2. Expand the section on `Mirroring repositories`
 3. In the field `Git repository URL`, enter the SSH clone address from the main repository. 
 
- <img src="img/img1.png">
+    <img src="img/img1.png">
 
 4. Select `Mirror Direction` as `Pull`
 5. Click on `Detect Host Keys`
@@ -30,9 +30,10 @@ You will see an entry in the table below the blue button. Often, there is an err
 
     <img src="img/copy-ssh-key.png" height="80">
 
-2. Then, browse to your profile picture (top right) and click on `Preferences`
-3. On the left of the page, click on `SSH keys`
-4. Paste the key (using CTRL+V or CMD+V) into the SSH field
-5. Click on `Add key`
+2. Then, browse to your profile picture (top left corner) and click on `Preferences`
+3. On the left of the page, click on `SSH Keys`
+4. Click on the 'Add new key' button on the SSH keys table
+5. Paste the key (using CTRL+V on Windows or CMD+V on macOS) into the SSH key field
+6. Click on `Add key`
 
 Now, the synchronization of the fork should perform successfully. You can click on the sync button or wait a few minutes. :white_check_mark:
diff --git a/external/contribute/ssh-key-generation/img/key-details.png b/external/contribute/ssh-key-generation/img/key-details.png
new file mode 100644
index 0000000000000000000000000000000000000000..a663151b4468f276f5d1ade6893c8b413cdc327d
Binary files /dev/null and b/external/contribute/ssh-key-generation/img/key-details.png differ
diff --git a/external/contribute/ssh-key-generation/img/new-key.png b/external/contribute/ssh-key-generation/img/new-key.png
new file mode 100644
index 0000000000000000000000000000000000000000..91e7e30d63166cf37dccec66250e7613fc1aa646
Binary files /dev/null and b/external/contribute/ssh-key-generation/img/new-key.png differ
diff --git a/external/contribute/ssh-key-generation/img/preferences.png b/external/contribute/ssh-key-generation/img/preferences.png
new file mode 100644
index 0000000000000000000000000000000000000000..bc428028a9d2761205aa1f1de0a347bff01b544e
Binary files /dev/null and b/external/contribute/ssh-key-generation/img/preferences.png differ
diff --git a/external/contribute/ssh-key-generation/img/ssh-menu.png b/external/contribute/ssh-key-generation/img/ssh-menu.png
new file mode 100644
index 0000000000000000000000000000000000000000..453da79e763cf5b82a472c8d72aea2d6f3553347
Binary files /dev/null and b/external/contribute/ssh-key-generation/img/ssh-menu.png differ
diff --git a/external/contribute/ssh-key-generation/ssh-key-generation.md b/external/contribute/ssh-key-generation/ssh-key-generation.md
new file mode 100644
index 0000000000000000000000000000000000000000..084d53f5a1c5dd489f6018963c6723c6b4572cd8
--- /dev/null
+++ b/external/contribute/ssh-key-generation/ssh-key-generation.md
@@ -0,0 +1,83 @@
+---
+layout: page
+permalink: /external/contribute/ssh-key-generation/
+shortcut: contribute:ssh-key-generation
+redirect_from:
+  - /cards/contribute:ssh-key-generation
+  - /external/cards/contribute:ssh-key-generation
+  - /contribute/ssh-key-generation
+  - /external/external/contribute/ssh-key-generation/
+---
+
+# Key-based Authentication on GitLab
+
+Key-based authentication allows GitLab users to identify their device once on their account and avoid having to log in via their credentials every time. GitLab uses SSH protocol to communicate with Git.
+
+SSH uses a public and a private key:
+- The public key must be registered in GitLab, where it "identifies" your device.
+- The private key must stay secret and preferably you should only keep it on a single device. The private key is the only key that can be used to authenticate your identity against the public key uploaded to GitLab -- if it becomes public, anyone can impersonate your identity and thus use your GitLab account. **Make sure you do NOT upload the private key anywhere by accident, not even to GitLab.**
+
+# Prerequisites
+
+To use SSH, one of the following must be installed on your device:
+
+- The OpenSSH client, which comes pre-installed on GNU/Linux, macOS, and [Windows 10 via Powershell or WSL](https://docs.gitlab.com/ee/user/ssh.html#use-ssh-on-microsoft-windows).
+- SSH version 6.5 or later. Earlier versions used an MD5 signature, which is not secure.
+
+To view the version of SSH installed on your system, run the following command in your terminal (on Linux or macOS) or Git Bash (on Windows):
+
+```
+ssh -V
+```
+
+# Key Generation
+
+> :warning: Please note that the steps below describe SSH key generation. If you already have one, **your existing key may be overwritten.**
+
+1. Start a terminal
+
+2. Type the following command at the command prompt and run it after replacing your firstname and lastname:
+  ```
+  ssh-keygen -t ed25519 -C firstname.lastname@uni.lu
+  ```
+3. Accept the suggested filename and directory
+
+4. Press `Enter` to continue. Defining a password is not necessary and can be skipped. 
+
+5. To copy the contents of your public key file into the clipboard, run the following command:
+
+    - For macOS:
+    ```
+    tr -d '\n' < ~/.ssh/id_ed25519.pub | pbcopy
+    ```
+    - For Windows:
+    ```
+    cat ~/.ssh/id_ed25519.pub | clip
+    ```
+
+# Saving the SSH Key on GitLab
+
+Once the content of the public key is copied in the clipboard, you need to register it with your GitLab account.
+
+To save your key to your account:
+
+1. Log in to GitLab using your LUMS account
+
+2. Navigate to the `Preferences` menu
+
+    ![preferences](img/preferences.png)
+3. User settings will be displayed on the left-hand side menu. Click on the `SSH Keys` option
+
+    ![ssh-menu](img/ssh-menu.png)
+
+4. On the `SSH Keys` page, click on `Add new key` button to add your public key
+
+    ![new-key](img/new-key.png)
+
+5. Paste your new key into the `Key` box, name the key and save it by clicking the `Add key` button
+
+    ![key-details](img/key-details.png)
+
+# Troubleshooting
+
+Please refer to the [GitLab Docs](https://docs.gitlab.com/ee/user/ssh.html#troubleshooting) or [create a ticket](https://service.uni.lu/sp?id=sc_cat_item&table=sc_cat_item&sys_id=c1d98bacdb9cf810ca53454039961917) for further assistance regarding the key-based authentication.
diff --git a/external/lab-equipment/electric-car/electric-car.md b/external/lab-equipment/electric-car/electric-car.md
index 3a4de8b01fb0858a29693b7245773c38d114e0b0..2c71cb0bd784136f901ccf61cc5ff58849288709 100644
--- a/external/lab-equipment/electric-car/electric-car.md
+++ b/external/lab-equipment/electric-car/electric-car.md
@@ -51,7 +51,7 @@ Send an email to the Instrument Care Team to inform them that you would like to
 
 ### Connect the car to the charging station
 
-- Check that the charging station is ON. If it is not the case, contact the instrument care team [instrument-care@uni.lu](instrument-care@uni.lu)
+- Check that the charging station is ON. If it is not the case, contact the instrument care team [instrument-care@uni.lu](mailto:instrument-care@uni.lu)
 
 <div align="center">
 <img src="img/img2.png" width="300">
diff --git a/external/lab-hsa/ppe/ppe.md b/external/lab-hsa/ppe/ppe.md
index a8104b6768616810fbd1f8cc0740887b706e1aa0..2264fcc80a64e2ad8733385b5a310ddcce5e9e83 100644
--- a/external/lab-hsa/ppe/ppe.md
+++ b/external/lab-hsa/ppe/ppe.md
@@ -15,10 +15,10 @@ redirect_from:
 
 To protect every person present in the laboratories from any contamination or exposure to hazardous materials, chemical or biological, each person entering the laboratories has to wear the appropriate Personal Protective Equipment (PPE).
 
-Every LCSB employees, students and visitors are responsible
+All LCSB employees, students and visitors are responsible
 for wearing the approriate PPE that will vary depending on the hazards present in the room, but must always include:
 
-- Your **lab coat** to protect yourself as it represents an additional layer of protection for skin in case of accidental contact and splashes of hazardous substances (chemical or biological). It is also a removable barrier and it protects body’s area not completely covered by clothing.The lab coat also prevent contamination inside and outside the lab.
+- Your **lab coat** to protect yourself as it represents an additional layer of protection for skin in case of accidental contact and splashes of hazardous substances (chemical or biological). It is also a removable barrier and it protects body’s area not completely covered by clothing. The lab coat also prevents contamination inside and outside the lab.
 
 - Appropriate **disposable gloves** (when handling biological materials or chemicals)
 
@@ -48,7 +48,7 @@ Exception is done for the doors marked by this sign:
 <div align="center">
 <img src="img/Gloves3.png" width="20%">
 </div>
-For Microscopes, computers and keyboard: stickers on the instruments indicates if gloves are required.
+For Microscopes, computers and keyboard: stickers on the instruments indicate if gloves are required.
 
 Important: 
 Do not touch face, hair, skin with your gloves.
@@ -71,7 +71,7 @@ Other protective measures have to be taken to reduce any contamination risk such
 
 Follow the [Docebo Training](https://unisupport.docebosaas.com/learn/course/52/covid-19-how-to-wear-protective-equipment) to know how to wear Personal Protective Equipment.
 
-More informations about lab coats can be found in the dedicated [How-To card]({{ '/?lab:lab-coats' | relative_url }}).
+More information about lab coats can be found in the dedicated [How-To card]({{ '/?lab:lab-coats' | relative_url }}).
 
 ## PPE Requirements
 
@@ -105,14 +105,14 @@ For regular biomolecular, chemical, cell culture or microbiology work in BSL 1 o
 
 - **Lab coat**
 
-Labcoat has to be tied up to top with sleeves fastened at the wrists, protecting the arms and torso.
+The Lab coat has to be tied up to top with sleeves fastened at the wrists, protecting the arms and torso.
 
 
 - **Disposable powder free nitrile gloves**
 
 Note: Disposable gloves must be discarded after each use or when they become contaminated.
 
-If the gloves are not contaminated, discard them in the domestic waste bin of the lab. Otherwise, follow the [chemical and biological waste concept]({{ '/?lab:waste' | relative_url }}).
+If the gloves are not contaminated, discard them in the domestic waste bins of the lab. Otherwise, follow the [chemical and biological waste concept]({{ '/?lab:waste' | relative_url }}).
 
 For activities with hazardous biological agents and harmful chemicals it is strongly recommended to use category III PPE gloves, and not medical exam gloves. 
 
@@ -329,16 +329,16 @@ Ensure protection against particles and limited protection against chemical vapo
 
 **PROTECT EYES AND SKIN FROM EXPOSURE TO UV LIGHT**
 
-- **Labcoat**
+- **Lab coat**
 
-Body needs to be fully covered with long trouser, closed shoes and labcoat. Labcoat has to be tied up to top with sleeves fastened at the wrists, protecting the arms and torso. Lab workers must be particularly vigilant to prevent gaps in protective clothing that commonly occur around the neck and wrist areas.
+Body needs to be fully covered with long trousers, closed shoes and lab coat. Lab coat has to be tied up to top with sleeves fastened at the wrists, protecting the arms and torso. Lab workers must be particularly vigilant to prevent gaps in protective clothing that commonly occur around the neck and wrist areas.
 
 - **Disposable powder free nitrile gloves**
 
 Hands must be protected with long purple nitrile gloves to ensure protection of the wrist.
 
 
-- **Faceshield**
+- **Face Shield**
 
 As soon as UV light is switched on, face shield is mandatory (if the protective glass of the equipment can not be closed completely). All the eye protection available in the lab will not fit for this purpose. Attention need to be paid to the specification of the PPE, in accordance with the safety officer.