Merge pull request #1195 from XhmikosR/xmr/md-040

Markdownlint: enable MD040 rule

Author: yubiuser

.markdownlint.json

@@ -32,7 +32,6 @@
   },
   "MD036": false,
   "MD038": false,
-  "MD040": false,
   "MD041": false,
   "MD045": false,
   "MD046": {

docs/api/auth.md

@@ -7,13 +7,13 @@ To get a session ID, you will have to send a `POST` request to the `/api/auth` e
 
     === "bash / cURL"
 
-        ``` bash
+        ```bash
         curl -k -X POST "https://pi.hole/api/auth" --data '{"password":"your-password"}'
         ```
 
     === "Python 3"
 
-        ``` python
+        ```python
         import requests
 
         url = "https://pi.hole/api/auth"
@@ -26,7 +26,7 @@ To get a session ID, you will have to send a `POST` request to the `/api/auth` e
 
     === "Javascript (plain)"
 
-        ``` javascript
+        ```javascript
         var data = JSON.stringify({"password":"your-password"});
         var xhr = new XMLHttpRequest();
 
@@ -39,7 +39,7 @@ To get a session ID, you will have to send a `POST` request to the `/api/auth` e
 
     === "Javascript (jQuery)"
 
-        ``` javascript
+        ```javascript
         $.ajax({
           url: "https://pi.hole/api/auth",
           type: "POST",
@@ -55,7 +55,7 @@ To get a session ID, you will have to send a `POST` request to the `/api/auth` e
 
     === "C"
 
-        ``` c
+        ```c
         #include <stdio.h>
         #include <stdlib.h>
         #include <curl/curl.h>
@@ -144,14 +144,14 @@ Note that when using cookie-based authentication, you will also need to send a `
 
     === "bash / cURL"
 
-        ``` bash
+        ```bash
         # Example: Authentication with SID in the request URI
         curl -k -X GET "https://pi.hole/api/dns/blocking?sid=vFA+EP4MQ5JJvJg+3Q2Jnw="
         ```
 
     === "Python 3"
 
-        ``` python
+        ```python
         # Example: Authentication with SID in the request header
         import requests
 
@@ -169,7 +169,7 @@ Note that when using cookie-based authentication, you will also need to send a `
 
     === "Javascript (plain)"
 
-        ``` javascript
+        ```javascript
         var data = null;
         var xhr = new XMLHttpRequest();
 
@@ -186,7 +186,7 @@ Note that when using cookie-based authentication, you will also need to send a `
 
     === "Javascript (jQuery)"
 
-        ``` javascript
+        ```javascript
         $.ajax({
           url: "https://pi.hole/api/dns/blocking",
           type: "GET",
@@ -220,13 +220,13 @@ If you have 2FA enabled for your Pi-hole, you will need to provide a TOTP token
 
     === "bash / cURL"
 
-        ``` bash
+        ```bash
         curl -k -X POST "https://pi.hole/api/auth" --data '{"password":"your-password", "totp":"123456"}'
         ```
 
     === "Python 3"
 
-        ``` python
+        ```python
         import requests
 
         url = "https://pi.hole/api/auth"
@@ -242,7 +242,7 @@ If you have 2FA enabled for your Pi-hole, you will need to provide a TOTP token
 
     === "Javascript (plain)"
 
-        ``` javascript
+        ```javascript
         var data = JSON.stringify({"password":"your-password", "totp":"123456"});
         var xhr = new XMLHttpRequest();
 
@@ -255,7 +255,7 @@ If you have 2FA enabled for your Pi-hole, you will need to provide a TOTP token
 
     === "Javascript (jQuery)"
 
-        ``` javascript
+        ```javascript
         $.ajax({
           url: "https://pi.hole/api/auth",
           type: "POST",
@@ -302,7 +302,7 @@ In addition to the status code, the server will also return a JSON object with m
 
     or
 
-    ``` json
+    ```json
     {
       "error": {
         "key": "bad_request",
@@ -325,14 +325,14 @@ To end your session before the SID expires, you can send a `DELETE` request to t
 
     === "bash / cURL"
 
-        ``` bash
+        ```bash
         # Example: Logout with SID in the request URI
         curl -k -X DELETE "https://pi.hole/api/auth?sid=vFA+EP4MQ5JJvJg+3Q2Jnw="
         ```
 
     === "Python 3"
 
-        ``` python
+        ```python
         # Example: Logout with SID in the request header
         import requests
 
@@ -349,7 +349,7 @@ To end your session before the SID expires, you can send a `DELETE` request to t
 
     === "Javascript (plain)"
 
-        ``` javascript
+        ```javascript
         var data = null;
         var xhr = new XMLHttpRequest();
 
@@ -365,7 +365,7 @@ To end your session before the SID expires, you can send a `DELETE` request to t
 
     === "Javascript (jQuery)"
 
-        ``` javascript
+        ```javascript
         $.ajax({
           url: "https://pi.hole/api/auth",
           type: "DELETE",

docs/api/index.md

@@ -21,7 +21,7 @@ The form of replies to successful requests strongly depends on the selected endp
 
     Response code: `HTTP/1.1 200 OK`
 
-    ``` json
+    ```json
     {
       "blocking": true
     }
@@ -45,7 +45,7 @@ In contrast, errors have a uniform, predictable style to ease their programmatic
 
     Response code: `HTTP/1.1 401 Unauthorized`
 
-    ``` json
+    ```json
     {
         "error": {
             "key": "unauthorized",
@@ -101,7 +101,7 @@ In contrast, errors have a uniform, predictable style to ease their programmatic
 
         Examples for a failed request with `hint` being set is (domain is already on this list):
 
-        ``` json
+        ```json
         {
             "error":  {
                 "key": "database_error",

docs/docker/build-image.md

@@ -4,7 +4,7 @@ In case you wish to customize the image, or perhaps check out a branch after bei
 
 In order to build the image locally, you will first need a copy of the repository on your computer. The following commands will clone the repository from Github and then put you into the directory
 
-```
+```bash
 git clone https://github.com/pi-hole/docker-pi-hole
 cd docker-pi-hole
 git checkout development #NOTE: This step is only needed until V6 is released
@@ -14,7 +14,7 @@ All other commands following assume you have at least run the above steps.
 
 ## Build.sh
 
-```
+```text
 Usage: ./build.sh [-l] [-f <ftl_branch>] [-c <core_branch>] [-w <web_branch>] [-t <tag>] [use_cache]
 Options:
   -f, --ftlbranch <branch>     Specify FTL branch (cannot be used in conjunction with -l)
@@ -37,7 +37,7 @@ When contributing, it's always a good idea to test your changes before submittin
 
 There is also `./build-and-test.sh`, which can be used to verify the tests that are run on Github pass with your changes.
 
-```
+```bash
 git checkout -b myNewFeatureBranch
 #make some changes
 ./build.sh
@@ -51,13 +51,13 @@ Occasionally you may need to try an alternative branch of one of the components
 
 - You have been asked by a developer to checkout the FTL branch `new/Sensors`. To do so
 
-```
+```bash
 ./build.sh -f new/Sensors
 ```
 
 - There is new docker-specific work being carried out on the branch `fix/logRotate` that you wish to test
 
-```
+```bash
 git checkout fix/logRotate
 ./build.sh
 ```
@@ -74,6 +74,6 @@ services:
 ...
 ```
 
-```
+```bash
 docker run [options] pihole:local
 ```

docs/docker/configuration.md

@@ -38,7 +38,6 @@ Array type configs should be delimited with `;`
 !!! note
     All FTL settings that are set via environment variables effectively become read-only, meaning that you will not be able to change them via the web interface or CLI. This is to ensure a "single source of truth" on the config. If you later unset or remove an environment variable, then FTL will revert to the default value for that setting
 
-
 An example of how some of these variables may look in your compose file
 
 ```yaml

docs/docker/index.md

@@ -49,7 +49,7 @@ Run `docker compose up -d` to build and start Pi-hole (on older systems, the syn
 
 The equivalent command for `docker run` would be:
 
-```
+```bash
 docker run --name pihole -p 53:53/tcp -p 53:53/udp -p 80:80/tcp -p 443:443/tcp -e TZ=Europe/London -e FTLCONF_webserver_api_password="correct horse battery staple" -e FTLCONF_dns_listeningMode=all -v ./etc-pihole:/etc/pihole -v ./etc-dnsmasq.d:/etc/dnsmasq.d --cap-add NET_ADMIN --restart unless-stopped pihole/pihole:latest
 ```
 

docs/docker/upgrading/index.md

@@ -28,4 +28,3 @@ docker rm pihole
 docker pull pihole/pihole:latest
 docker run [ ... arguments (see Getting Started) ... ]
 ```
-

docs/docker/upgrading/v5-v6.md

@@ -41,7 +41,7 @@ Nearly all environment variables from previous versions have been removed, but f
 
 Reverse server (`REV_SERVER*`) variables should be replaced with the single `FTLCONF_dns_revServers`, which accepts an array of reverse servers (delimited by `;`) in the following format:
 
-```
+```text
 <enabled>,<ip-address>[/<prefix-len>],<server>[#<port>],<domain>
 ```
 
@@ -54,7 +54,7 @@ If, for example, you had the following old style variables:
 
 You would now set:
 
-```
+```text
 FTLCONF_dns_revServers: 'true,192.168.0.0/24,192.168.0.1#53,lan'
 ```
 
@@ -65,10 +65,8 @@ By default, Pi-hole v6 no longer reads configuration files from `/etc/dnsmasq.d/
 1. Mount the local folder containing the config files into `/etc/dnsmasq.d` into the container
 2. Set the environment variable `FTLCONF_misc_etc_dnsmasq_d: 'true'`
 
-
 If you only want to add a single/few `dnsmasq` config lines you can use the variable `FTLCONF_misc_dnsmasq_lines`. Each line should be separated with `;`
 
-
 ### Removed Variables
 
 The following variables can be removed without replacement, as they are no longer used:
@@ -93,4 +91,3 @@ The following variables can be removed without replacement, as they are no longe
 - `WEB_UID`
 - `WEBLOGS_STDOUT`
 - `WEBPASSWORD_FILE`
-

docs/ftldns/blockingmode.md

@@ -14,7 +14,7 @@ In `NULL` mode, which is both the default and recommended mode for Pi-hole *FTL*
 
 A blocked query would look like the following:
 
-```
+```text
 ;; QUESTION SECTION:
 ;doubleclick.net.               IN      ANY
 
@@ -40,7 +40,7 @@ In `IP-NODATA-AAAA` mode, blocked queries will be answered with the local IPv4 a
 
 Assuming your Pi-hole server is at `192.168.1.42`, then a blocked query would look like the following:
 
-```
+```text
 ;; QUESTION SECTION:
 ;doubleclick.net.               IN      ANY
 
@@ -64,7 +64,7 @@ The IP that is returned is automatically determined by FTL, however it can also
 
 A blocked query would look like the following:
 
-```
+```text
 ;; QUESTION SECTION:
 ;doubleclick.net.               IN      ANY
 
@@ -88,7 +88,7 @@ In `NXDOMAIN` mode, blocked queries will be answered with an empty response (i.e
 
 A blocked query would look like the following:
 
-```
+```text
 ;; QUESTION SECTION:
 ;doubleclick.net.               IN      ANY
 ```
@@ -101,10 +101,9 @@ In `NODATA` mode, blocked queries will be answered with an empty response (no an
 
 A blocked query would look like the following:
 
-```
+```text
 ;; QUESTION SECTION:
 ;doubleclick.net.               IN      ANY
 ```
 
 **Advantages & Disadvantages:** This mode is similar to `NXDOMAIN` blocking mode. Clients might have a better acceptance of `NODATA` replies compared to `NXDOMAIN` replies.
-