change bash codefence to console

Signed-off-by: Phill Kelley <[email protected]>

Author: Paraphraser

docs/Containers/Pi-hole.md

@@ -68,15 +68,15 @@ It is important to realise that `WEBPASSWORD` only has any effect on the very **
 
 If `WEBPASSWORD` is **not** set on first launch, Pi-hole defaults to a randomly-generated password which you can discover after the first launch like this:
 
-```bash
+```console
 $ docker logs pihole | grep random 
 ```
 
 > Remember, docker logs are ephemeral so you need to run that command before the log disappears!
 
 If you ever need to reset Pi-hole's admin password to a known value, use the following command:
 
-```bash
+```console
 $ docker exec pihole pihole -a -p mybigsecret
 ```
 
@@ -206,7 +206,7 @@ Keep in mind that many Raspberry Pis have both Ethernet and WiFi interfaces. It
 
 You can use the following command to discover the MAC addresses for your Raspberry Pi's Ethernet and WiFi interfaces:
 
-```bash
+```console
 $ for I in eth0 wlan0 ; do ip link show $I ; done
 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
     link/ether dc:a6:32:4c:89:f9 brd ff:ff:ff:ff:ff:ff
@@ -227,7 +227,7 @@ The Raspberry Pi itself does **not** have to use the Pi-hole container for its o
 
 Nevertheless, if you configure Pi-hole to be [authoritative for local domain names](#localNames) (eg `raspberrypi.home.arpa`) then you will probably want to configure your Raspberry Pi to use the Pi-hole container in the first instance, and then fall back to an alternative if the container is down. Here is an example of how to do that:
 
-```bash
+```console
 $ echo "name_servers=127.0.0.1" | sudo tee -a /etc/resolvconf.conf
 $ echo "name_servers_append=8.8.8.8" | sudo tee -a /etc/resolvconf.conf
 $ echo "resolv_conf_local_only=NO" | sudo tee -a /etc/resolvconf.conf
@@ -250,7 +250,7 @@ In words:
 
 	You need slightly different syntax if you want to add multiple fallback servers. For example, suppose your fallback hosts are a local server (eg 192.168.1.2) running BIND9 and 8.8.8.8. The command would be:
 
-	```bash
+	```console
 	$ echo 'name_servers_append="192.168.1.2 8.8.8.8"' | sudo tee -a /etc/resolvconf.conf
 	```
 
@@ -274,7 +274,7 @@ Make these assumptions:
 
 The result of the configuration appears in `/etc/resolv.conf`:
 
-```bash
+```console
 $ cat /etc/resolv.conf
 # Generated by resolvconf
 nameserver 127.0.0.1
@@ -294,15 +294,15 @@ Notes:
 
 * If you wish to prevent the Raspberry Pi from including the address(es) of DNS servers learned from DHCP, you can instruct the DHCP client running on the Raspberry Pi to ignore the information coming from the DHCP server:
 
-	```bash
+	```console
 	$ echo 'nooption domain_name_servers' | sudo tee -a /etc/dhcpcd.conf
 	$ sudo service dhcpcd reload
 	$ sudo resolvconf -u 
 	```
 
 * If you have followed the steps in [Adding local domain names](#localNames) to define names for your local hosts, you can inform the Raspberry Pi of that fact like this:
 
-	```bash
+	```console
 	$ echo 'search_domains=home.arpa' | sudo tee -a /etc/resolvconf.conf
 	$ sudo resolvconf -u 
 	```
@@ -346,21 +346,21 @@ If you need help, try asking questions on the [IOTstack Discord channel](https:/
 
 Install dig:
 
-```bash
+```console
 $ apt install dnsutils
 ```
 
 Test that Pi-hole is correctly configured (should respond 192.168.1.10):
 
-```bash
+```console
 $ dig raspberrypi.home.arpa @192.168.1.10
 ```
 
 To test on your desktop if your network configuration is correct, and an ESP
 will resolve its DNS queries correctly, restart your desktop machine to ensure
 DNS changes are updated and then use:
 
-```bash
+```console
 $ dig raspberrypi.home.arpa
 ```
 
@@ -397,7 +397,7 @@ The recommended approach is:
 3. Logout of the Web GUI.
 4. Run the following commands:
 
-	```bash
+	```console
 	$ cd ~/IOTstack
 	$ docker-compose rm --force --stop -v pihole
 	$ sudo rm -rf ./volumes/pihole