Updated documentation

docs/manual/_sources/hardware.rst.txt

@@ -210,6 +210,12 @@ and start communicating over them using Reticulum. It is not necessary to enable
 infrastructure such as DHCP servers, DNS or similar, as long as at least Ethernet is
 available, and packets are passed transparently over the physical WiFi-based devices.
 
+.. image:: graphics/radio_rblhg5.png
+    :width: 49%
+
+.. image:: graphics/radio_is5ac.png
+    :width: 49%
+
 Below is a list of example WiFi (and similar) radios that work well for high capacity
 Reticulum links over long distances:
 

docs/manual/hardware.html

@@ -208,6 +208,8 @@ Most devices will behave like this by default, or allow it via configuration opt
 and start communicating over them using Reticulum. It is not necessary to enable any IP
 infrastructure such as DHCP servers, DNS or similar, as long as at least Ethernet is
 available, and packets are passed transparently over the physical WiFi-based devices.</p>
+<a class="reference internal image-reference" href="_images/radio_rblhg5.png"><img alt="_images/radio_rblhg5.png" src="_images/radio_rblhg5.png" style="width: 49%;" /></a>
+<a class="reference internal image-reference" href="_images/radio_is5ac.png"><img alt="_images/radio_is5ac.png" src="_images/radio_is5ac.png" style="width: 49%;" /></a>
 <p>Below is a list of example WiFi (and similar) radios that work well for high capacity
 Reticulum links over long distances:</p>
 <ul class="simple">

docs/source/hardware.rst

@@ -210,6 +210,12 @@ and start communicating over them using Reticulum. It is not necessary to enable
 infrastructure such as DHCP servers, DNS or similar, as long as at least Ethernet is
 available, and packets are passed transparently over the physical WiFi-based devices.
 
+.. image:: graphics/radio_rblhg5.png
+    :width: 49%
+
+.. image:: graphics/radio_is5ac.png
+    :width: 49%
+
 Below is a list of example WiFi (and similar) radios that work well for high capacity
 Reticulum links over long distances: