Remove extraneous tab characters throughout

Author: Paraphraser

docs/Containers/Mosquitto.md

@@ -179,9 +179,9 @@ Using `mosquitto.conf` as the example, assume you wish to use your existing file
 	$ cd ~/IOTstack
 	$ sudo mv ./services/mosquitto/mosquitto.conf ./volumes/mosquitto/config/mosquitto.conf
 	```
-	
+
 	> The move overwrites the default. At this point, the moved file will probably be owned by user "pi" but that does not matter.
-	
+
 2. Mosquitto will always enforce correct ownership (1883:1883) on any restart but it will not overwrite permissions. If in doubt, use mode 644 as your default for permissions:
 
 	```bash
@@ -193,7 +193,7 @@ Using `mosquitto.conf` as the example, assume you wish to use your existing file
 	```bash
 	$ docker-compose restart mosquitto
 	```
-	
+
 4. Check your work:
 
 	```bash
@@ -279,7 +279,7 @@ A common problem with the previous version of Mosquitto for IOTstack occurred wh
 The Mosquitto container performs self-repair each time the container is brought up or restarts. If `pwfile` is missing, an empty file is created as a placeholder. This prevents the restart loop. What happens next depends on `allow_anonymous`:
 
 * If `true` then:
-	
+
 	- Any MQTT request *without* credentials will be permitted;
 	- Any MQTT request *with* credentials will be rejected (because `pwfile` is empty so there is nothing to match on).
 
@@ -292,17 +292,17 @@ To create a username and password, use the following as a template.
 ```
 $ docker exec mosquitto mosquitto_passwd -b /mosquitto/pwfile/pwfile «username» «password» 
 ```
-		
+
 Replace «username» and «password» with appropriate values, then execute the command. For example, to create the username "hello" with password "world":
-	
+
 ```
 $ docker exec mosquitto mosquitto_passwd -b /mosquitto/pwfile/pwfile hello world
 ```
 
 Note:
 
 * See also [customising health-check](#healthCheckCustom). If you are creating usernames and passwords, you may also want to create credentials for the health-check agent.
-	
+
 #### <a name="checkPasswordFile"> check password file </a>
 
 There are two ways to verify that the password file exists and has the expected content:
@@ -312,7 +312,7 @@ There are two ways to verify that the password file exists and has the expected
 	```bash
 	$ sudo cat ~/IOTstack/volumes/mosquitto/pwfile/pwfile 
 	```
-	
+
 	> `sudo` is needed because the file is neither owned nor readable by `pi`.
 
 2. View the file using its **internal** path:
@@ -346,24 +346,24 @@ There are several ways to reset the password file. Your options are:
 	$ sudo rm ./volumes/mosquitto/pwfile/pwfile
 	$ docker-compose restart mosquitto 
 	```
-	
+
 	The result is an empty password file.
-	
+
 2. Clear all existing passwords while adding a new password:
 
 	```bash
 	$ docker exec mosquitto mosquitto_passwd -c -b /mosquitto/pwfile/pwfile «username» «password»
 	```
-	
+
 	The result is a password file with a single entry.
-	
+
 3. Clear all existing passwords in favour of a single dummy password which is then removed:
 
 	```bash
 	$ docker exec mosquitto mosquitto_passwd -c -b /mosquitto/pwfile/pwfile dummy dummy
 	$ docker exec mosquitto mosquitto_passwd -D /mosquitto/pwfile/pwfile dummy
 	```
-	
+
 	The result is an empty password file.
 
 ### <a name="activateSecurity"> Activate Mosquitto security </a>
@@ -379,7 +379,7 @@ There are several ways to reset the password file. Your options are:
 	```
 	#password_file /mosquitto/pwfile/pwfile
 	```
-	
+
 	so that it becomes:
 
 	```
@@ -391,14 +391,14 @@ There are several ways to reset the password file. Your options are:
 	```
 	allow_anonymous true
 	```
-	
+
 	If `true` then:
-	
+
 	* Any MQTT request without credentials will be permitted;
 	* The validity of credentials supplied with any MQTT request will be enforced.
 
 	If `false` then:
-	
+
 	* Any MQTT request without credentials will be rejected;
 	* The validity of credentials supplied with any MQTT request will be enforced.
 
@@ -462,7 +462,7 @@ $ mosquitto_sub -v -h 127.0.0.1 -p 1883 -t "/password/test" -F "%I %t %p" -u hel
 ```
 
 Repeat the earlier test:
-	
+
 ```
 $ mosquitto_pub -h 127.0.0.1 -p 1883 -t "/password/test" -m "up up and away" -u hello -P world
 2021-02-16T14:40:51+1100 /password/test up up and away
@@ -471,7 +471,7 @@ $ mosquitto_pub -h 127.0.0.1 -p 1883 -t "/password/test" -m "up up and away" -u
 Note:
 
 * the second line above is coming from the `mosquitto_sub` running in the background.
-	
+
 When you have finished testing you can kill the background process (press return twice after you enter the `kill` command):
 
 ```
@@ -493,7 +493,7 @@ The agent is invoked 30 seconds after the container starts, and every 30 seconds
 	```
 	iotstack/mosquitto/healthcheck
 	```
-	
+
 * Subscribes to the same broker for the same topic for a single message event.
 * Compares the payload sent with the payload received. If the payloads (ie time-stamps) match, the agent concludes that the Mosquitto broker (the process running inside the same container) is functioning properly for round-trip messaging.
 
@@ -529,7 +529,7 @@ Possible reply patterns are:
 	NAMES       STATUS
 	mosquitto   Up About a minute (unhealthy)
 	```
-	
+
 You can also subscribe to the same topic that the health-check agent is using to view the retained messages as they are published:
 
 ```bash
@@ -553,16 +553,16 @@ You can customise the operation of the health-check agent by editing the `mosqui
 	    environment:
 	      - HEALTHCHECK_PORT=12345
 	```
-	
+
 2. If the default topic string used by the health-check agent causes a name-space collision, you can override it. For example, you could use a Universally-Unique Identifier (UUID):
 
 	```yaml
 	    environment:
 	      - HEALTHCHECK_TOPIC=4DAA361F-288C-45D5-9540-F1275BDCAF02
 	```
-	
+
 	Note:
-	
+
 	* You will also need to use the same topic string in the `mosquitto_sub` command shown at [monitoring health-check](#healthCheckMonitor).
 
 3. If you have enabled authentication for your Mosquitto broker service, you will need to provide appropriate credentials for your health-check agent:
@@ -581,15 +581,15 @@ You can customise the operation of the health-check agent by editing the `mosqui
 	```
 
 	Notes:
-	
+
 	* The directives to disable health-checking are independent of the environment variables. If you want to disable health-checking temporarily, there is no need to remove any `HEALTHCHECK_` environment variables that may already be in place.
-	* Conversely, the mere presence of a `healthcheck:` clause in the `mosquitto` service definition overrides the supplied agent. In other words, the following can't be used to re-enable the supplied agent:	
+	* Conversely, the mere presence of a `healthcheck:` clause in the `mosquitto` service definition overrides the supplied agent. In other words, the following can't be used to re-enable the supplied agent:
 
 		```yaml
 		    healthcheck:
 		      disable: false
 		```
-		
+
 		You must remove the entire `healthcheck:` clause.
 
 ## <a name="upgradingMosquitto"> Upgrading Mosquitto </a>
@@ -665,7 +665,7 @@ If you need to pin Mosquitto to a particular version:
 	``` 
 
 	The new *local image* is built, then the new container is instantiated based on that image. The `prune` deletes the old *local image*.
-	
+
 Note:
 
 * As well as preventing Docker from updating the *base image*, pinning will also block incoming updates to the *Dockerfile* from a `git pull`. Nothing will change until you decide to remove the pin.
@@ -701,7 +701,7 @@ If you have a use-case that needs port 9001, you can re-enable support by:
 	listener 1883
 	listener 9001
 	```
-	
+
 	You need **both** lines. If you omit 1883 then Mosquitto will stop listening to port 1883 and will only listen to port 9001.
 
 3. Restarting the container: