Merge branch 'master' into topography

docs/configuration/radio/lora.mdx

@@ -57,6 +57,8 @@ The Presets available are as follows, and follow a linear pattern of Fastest \<\
 
 Maximum number of hops. This can't be greater than 7. Default is 3 which should be fine for most applications. _**Really, 3 is fine.**_
 
+![Hop Count](/img/configuration/max-hops.png)
+
 ### Transmit Power
 
 If zero then, use default max legal continuous power (i.e. something that won't burn out the radio hardware)

docs/software/mqtt/index.mdx

@@ -7,6 +7,8 @@ sidebar_position: 6
 
 ## Bridging networks
 
+![Common MQTT Layout](/img/software/mqtt/mqtt.png)
+
 Meshtastic networks in different locations beyond the reach of LoRa can be easily bridged together using MQTT. The simplest option is to connect your mesh to the official Meshtastic MQTT broker. This makes your devices appear on the world map, and provides a copy of your mesh traffic, translated into JSON. All you have to do to join the public MQTT server is to Enable MQTT and set Uplink and Downlink on the channels that you want to share over MQTT. The default device configuration using the public MQTT Server is encrypted.
 
 You can also share channel settings with a remote network. If you use the default Meshtastic MQTT server, packets are always encrypted. If you use a custom MQTT broker (ie set `mqtt.address`), the `mqtt.encryption_enabled` setting applies, which by default is false. You can also specify your own private MQTT broker and specify authentication for that broker to bridge several mesh networks together, via the internet (or just a local IP network).