docs/pi-hole: consistently use the same example IP

Fix to assume your RPi IP-address being 192.168.1.10 in all examples.
Previously some parts of the doc assumed 192.168.1.50.

Author: ukkopahis

docs/Containers/Pi-hole.md

@@ -183,7 +183,7 @@ where «your_ip» can be:
 Login to the Pi-hole web interface: `http://raspberrypi.local:8089/admin`:
 
 1. Select from Left menu: Local DNS -> DNS Records
-2. Enter Domain: `raspberrypi.home.arpa` and IP Address: `192.168.1.10`.
+2. Enter Domain: `raspberrypi.home.arpa` and the RPi's IP Address, e.g. `192.168.1.10`.
 3. Press Add.
 
 Now you can use `raspberrypi.home.arpa` as the domain name for the Raspberry Pi
@@ -269,26 +269,26 @@ Make these assumptions:
 	resolv_conf_local_only=NO
 	```
 
-2. The Raspberry Pi running Pi-hole has the IP address 192.168.1.50 which it obtains as a static assignment from your DHCP server.
-3. You have configured your DHCP server to provide 192.168.1.50 for client devices to use to obtain DNS services (ie, you are saying clients should use Pi-hole for DNS). 
+2. The Raspberry Pi running Pi-hole has the IP address 192.168.1.10 which it obtains as a static assignment from your DHCP server.
+3. You have configured your DHCP server to provide 192.168.1.10 for client devices to use to obtain DNS services (ie, you are saying clients should use Pi-hole for DNS).
 
 The result of the configuration appears in `/etc/resolv.conf`:
 
 ```console
 $ cat /etc/resolv.conf
 # Generated by resolvconf
 nameserver 127.0.0.1
-nameserver 192.168.1.50
+nameserver 192.168.1.10
 nameserver 8.8.8.8
 ```
 
 Interpretation:
 
 * `nameserver 127.0.0.1` is present because of `name_servers=127.0.0.1`
-* `nameserver 192.168.1.50` is present because it was learned from DHCP
+* `nameserver 192.168.1.10` is present because it was learned from DHCP
 * `nameserver 8.8.8.8` is present because of `name_servers_append=8.8.8.8`
 
-The fact that the Raspberry Pi is effectively represented twice (once as 127.0.0.1, and again as 192.168.1.50) does not matter. If the Pi-hole container stops running, the Raspberry Pi will bypass 192.168.1.50 and fail over to 8.8.8.8, failing back to 127.0.0.1 when the Pi-hole container starts again.
+The fact that the Raspberry Pi is effectively represented twice (once as 127.0.0.1, and again as 192.168.1.10) does not matter. If the Pi-hole container stops running, the Raspberry Pi will bypass 192.168.1.10 and fail over to 8.8.8.8, failing back to 127.0.0.1 when the Pi-hole container starts again.
 
 Notes: