Markdown link check

.github/workflows/check-links.yaml

@@ -11,4 +11,4 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@master
-      - uses: gaurav-nelson/github-action-markdown-link-check@v1
+      - uses: tcort/github-action-markdown-link-check@v1

README.md

@@ -102,7 +102,7 @@ Thanks go to these wonderful people ([emoji key](https://allcontributors.org/doc
 
 <!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
 <!-- prettier-ignore-start -->
-<!-- markdownlint-disable -->
+<!-- markdown-link-check-disable -->
 <table>
   <tr>
     <td align="center"><a href="http://includeio.stream/"><img src="https://avatars.githubusercontent.com/u/1433152?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Abhishek L</b></sub></a><br /><a href="#content-theanalyst" title="Content">🖋</a></td>
@@ -121,7 +121,6 @@ Thanks go to these wonderful people ([emoji key](https://allcontributors.org/doc
   </tr>
 </table>
 
-<!-- markdownlint-restore -->
 <!-- prettier-ignore-end -->
 
 <!-- ALL-CONTRIBUTORS-LIST:END -->

exercises/README.md

@@ -110,8 +110,7 @@ Each exercise is in a subdirectory with mainly 4 sets of files
 Examples of working environments
 ================================
 
-Using lxplus
-------------
+## Using lxplus
 
   - lxplus9 at CERN is perfectly suitable for the exercises
   - it has all the needed compilers/tools
@@ -125,35 +124,34 @@ make
 ./hello
 ```
 
-Using OS/X
-----------
+## Using OS/X
+
 - Install xcode and the command line tools
 - Compiling, running, debugging will work, but a few tools such as valgrind are not available
 
 
-
-Using Windows
--------------
+## Using Windows
 
 There are multiple options if you bring a Windows machine to the course:
 
 1. Use the Windows Subsystem for Linux (WSL)
 2. Use an ssh client and connect to lxplus
 3. Use Visual Studio and the native Windows compiler (MSVC)
 
-We advise to use either [WSL](#wsl) or [lxplus](#lxplus), so a non-Windows experience.
+We advise to use either [WSL](#wsl) or [lxplus](#using-lxplus), so a non-Windows experience.
 This way, you can follow all exercises, especially the ones on tools, which are mostly Linux focused.
 Also, we can ensure that mentors can help you in case you get stuck.
 Using lxplus is probably the easiest, but if you have a really hard time using the terminal,
 you can go for WSL and use Visual Studio Code.
 
 ### WSL
 
+<!-- markdown-link-check-disable-next-line -->
 Important: if you have [VirtualBox](https://www.virtualbox.org/) installed on Windows do not try to install WSL2,
 due to [this issue](https://github.com/MicrosoftDocs/WSL/issues/798).
 It will either not work or run very slow.
 Instead, we recommend you use VirtualBox directly to set up a suitable virtualised Linux environment.
-Or use [lxplus](#lxplus).
+Or use [lxplus](#using-lxplus).
 
 The procedure is described in detail [here](https://docs.microsoft.com/en-us/windows/wsl/install).