Merge pull request #373 from ot0tot/Fix-hotlinked-images

Fix hotlinked images

docs/hardware/crystal-frequency-error.md

@@ -121,7 +121,7 @@ Just to note, we've had some mismatching cases as follows:
 </figure>
 
 <figure markdown>
-![flywoo_caps](https://cdn.discordapp.com/attachments/798006228450017290/1008232318135193611/SimoneFrascarelli.jpg)
+![flywoo_caps](../assets/images/SimoneFrascarelli.jpg)
 <figcaption>Flywoo Caps</figcaption>
 </figure>
 

docs/hardware/smd-antenna.md

@@ -12,7 +12,7 @@ Have you ever wished you could build a quad without worrying about how to mount
 If so, the SMD Antenna is for you!  
 
 <figure markdown>
-<img class="center-img" src="https://media.discordapp.net/attachments/738450139693449258/834252910422392832/IMG_0665.JPG?width=910&height=682" width="40%">
+<img class="center-img" src="../assets/images/IMG_0665.JPG" width="40%">
 <figcaption>SMD Antenna</figcaption>
 </figure>
 
@@ -32,11 +32,11 @@ This perky little fellow is worse at receiving signals than his snaky brothers,
     The antenna is sort of fragile and can break off or be melted by a stray soldering iron. If this happens, you can save your receiver by soldering a U.FL/IPEX1 connector onto the pads as shown here. Just make sure the center pin has continuity with the filter at the other end of the trace, and no continuity with the ground.  
 
 <figure markdown>
-<img class="center-img" src="https://media.discordapp.net/attachments/738450139693449258/834252903141212210/IMG_0456.jpg?width=910&height=682" width="40%">
+<img class="center-img" src="../assets/images/IMG_0456.jpg" width="40%">
 </figure>
 
 Conversely, the SMD antenna can be soldered to regular U.FL footprints if you're brave.  
 
 <figure markdown>
-<img class="center-img" src="https://media.discordapp.net/attachments/738450139693449258/834258069265317898/IMG_0380_1.jpg?width=326&height=267">
+<img class="center-img" src="../assets/images/IMG_0380_1.jpg">
 </figure>

docs/hardware/special-targets/diy-tx.md

@@ -17,15 +17,15 @@ Possibly one of the biggest benefits of using `ExpressLRS` is custom hardware!
 All of the info on this topic can be found [here](https://github.com/ExpressLRS/ExpressLRS-Hardware/tree/master/PCB/2400MHz/TX_SX1280)
 
 <figure markdown>
-<img class="center-img" src="https://cdn.discordapp.com/attachments/738450139693449258/772053169735467018/image0.jpg" width=40%>
+<img class="center-img" src="../../assets/images/diytx0.jpg" width=40%>
 </figure>
 
 ### Custom Super Slim ESP 2.4 GHz TX (for lite module bay)
 
 The super slim is an evolution of the slim. It uses the same base hardware as the JR size one. It's the same size as an R9M Lite, and fits in all handsets with a lite module bay such as the X-Lite, X9 Lite, and Tango 2 (with the proper adapter). The rest of the info can be found [here](https://github.com/ExpressLRS/ExpressLRS-Hardware/tree/master/PCB/2400MHz/TX_SX1280_Super_Slim)
 
 <figure markdown>
-<img class="center-img" src="https://cdn.discordapp.com/attachments/596350022191415320/804895358329028618/image0.jpg" width=40%>
+<img class="center-img" src="../../assets/images/diytx1.jpg" width=40%>
 </figure>
 
 ### Custom 900 MHz TX (not built anymore)

docs/hardware/special-targets/nuclear-hardware.md

@@ -17,7 +17,7 @@ The Nuclear RX is designed to be as small as possible, using the same software t
 - Up to 500Hz packet rate  
 
 <figure markdown>
-<img class="center-img" src="https://media.discordapp.net/attachments/738450139693449258/834252910422392832/IMG_0665.JPG?width=910&height=682" width="40%">
+<img class="center-img" src="../../assets/images/IMG_0665.jpg" width="40%">
 </figure>
 
 When you get your Nuclear RX, it will likely be on the latest release firmware. You'll probably have to update it to work with your TX. To update, follow the steps in the [Wi-Fi updating](../../software/updating/wifi-updating.md) page. Alternatively, you can use [betaflight passthrough](../../software/updating/betaflight-passthrough.md) should work, but the boot jumper must be bridged while applying power to the RX.
@@ -34,7 +34,7 @@ When building, use one of the `DIY_2400_RX_ESP8285_SX1280_via_X` targets. To use
 If for some reason the RX needs to be in boot mode, bridge the jumpers as shown here:
 
 <figure markdown>
-<img class="center-img" src="https://cdn.discordapp.com/attachments/738450139693449258/858365975489019974/Capture.PNG" width="40%">
+<img class="center-img" src="../../assets/images/Capture.png" width="40%">
 </figure>
 
 ## Nuclear TX

docs/info/signal-health.md

@@ -49,9 +49,9 @@ In iNAV, the RSSI Value on the OSD is called RSSI (Signal Strength), and will al
 ## RF Mode Indexes (RFMD)
 OSDs report the packet rate using an index instead of the actual rate, either as a `RATE:LQ%` or with rate in the hundreds digit such as `799` where 7 is the RATE and 99 is the LQ%. Handsets display the rate using the RFMD telemetry item.
 
-![OSD RFMD](https://cdn.discordapp.com/attachments/738450139693449258/886313969638334484/unknown.png)
+![OSD RFMD](../assets/images/OSD_RFMD.png)
 
-| RFMD | Lua | Packet Rate | Sensitivity <br />Limit | TX duration <br />(us) | TX Interval <br/>(us) |
+| RFMD | Lua | Packet Rate | Sensitivity <br/>Limit | TX Duration <br/>(us) | TX Interval <br/>(us) |
 |:---:|:---:|:---:|---:|---:|---:|
 | 14 | D50 | 50Hz | -112dBm | 4640.0 | 5000 |
 | 13 | F1000 | 1000Hz | -104dBm | 388.8 | 1000 |

docs/quick-start/binding.md

@@ -64,7 +64,7 @@ For traditional binding to work, a Binding Phrase must not be set, at least for
 The Receiver LED should also be blinking when powered up.
 
 <figure markdown>
-![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
+![LEDSEQ_DISCONNECTED](../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)
 </figure>
 
 ??? danger "Receiver LED doesn't Blink (click/tap to expand)"
@@ -103,7 +103,7 @@ The procedure is as follows:
 3. Make sure the LED is doing a quick double-blink, which indicates the receiver is in bind mode.
 
     <figure markdown>
-    ![LEDSEQ_BINDING](https://cdn.discordapp.com/attachments/738450139693449258/921065812763218010/LEDSEQ_BINDING_10_10_10_100.gif)
+    ![LEDSEQ_BINDING](../assets/images/LEDSEQ_BINDING_10_10_10_100.gif)
     </figure>
 
 4. Power up your transmitter/radio and use the ++"[BIND]"++ button on the ExpressLRS Lua script, which sends out a binding pulse. The Popup will briefly show up and then disappear.
@@ -115,7 +115,7 @@ The procedure is as follows:
 5. If the receiver LED turned into a solid light, it's bound!
 
     <figure markdown>
-    ![CONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812507373568/LED_ON.gif)
+    ![CONNECTED](../assets/images/LED_ON.gif)
     </figure>
 
 ## Connection Check
@@ -154,7 +154,7 @@ Using the [ExpressLRS Lua Script](transmitters/lua-howto.md), look for a `C` in
     This is also indicated by the Receiver LED as 3 fast blinks then a pause:
 
     <figure markdown>
-    ![LEDSEQ_MODEL_MISMATCH](https://cdn.discordapp.com/attachments/738450139693449258/921065813425934446/LEDSEQ_MODEL_MISMATCH_10_10_10_10_10_100.gif)
+    ![LEDSEQ_MODEL_MISMATCH](../assets/images/LEDSEQ_MODEL_MISMATCH_10_10_10_10_10_100.gif)
     </figure>
 
     If you've deliberately set up Model Matching following [this page](../software/model-config-match.md), make sure your settings are correct.

docs/quick-start/led-status.md

@@ -27,12 +27,12 @@ Receivers with a single color LED communicate their status as follows:
 
 || LED Indication | Status |
 |---|---|---|
-|![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)| Slow blink 500ms on/off | Waiting for connection from transmitter |
-|![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)| Fast blinking 25ms on/off | WiFi mode enabled |
-|![LEDSEQ_RADIO_FAILED](https://cdn.discordapp.com/attachments/738450139693449258/921065813719527464/LEDSEQ_RADIO_FAILED_20_100.gif)| Medium speed blink 100ms on/off | Radio chip not detected |
-|![LEDSEQ_BINDING](https://cdn.discordapp.com/attachments/738450139693449258/921065812763218010/LEDSEQ_BINDING_10_10_10_100.gif)| Double blink then pause | Binding mode enabled |
-|![LEDSEQ_MODEL_MISMATCH](https://cdn.discordapp.com/attachments/738450139693449258/921065813425934446/LEDSEQ_MODEL_MISMATCH_10_10_10_10_10_100.gif)| Triple blink then pause | Connected to transmitter but mismatched model-match configuration |
-|![CONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812507373568/LED_ON.gif)| Solid on | Connected to a transmitter, or bootloader mode enabled |
+|![LEDSEQ_DISCONNECTED](../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)| Slow blink 500ms on/off | Waiting for connection from transmitter |
+|![LEDSEQ_WIFI_UPDATE](../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)| Fast blinking 25ms on/off | WiFi mode enabled |
+|![LEDSEQ_RADIO_FAILED](../assets/images/LEDSEQ_RADIO_FAILED_20_100.gif)| Medium speed blink 100ms on/off | Radio chip not detected |
+|![LEDSEQ_BINDING](../assets/images/LEDSEQ_BINDING_10_10_10_100.gif)| Double blink then pause | Binding mode enabled |
+|![LEDSEQ_MODEL_MISMATCH](../assets/images/LEDSEQ_MODEL_MISMATCH_10_10_10_10_10_100.gif)| Triple blink then pause | Connected to transmitter but mismatched model-match configuration |
+|![CONNECTED](../assets/images/LED_ON.gif)| Solid on | Connected to a transmitter, or bootloader mode enabled |
 
 Receivers with RGB LED show status as indicated below:
 

docs/quick-start/pre-1stflight.md

@@ -80,7 +80,7 @@ On the 900MHz hardware, a value of -20dBm or thereabouts is a good indication yo
 - Check if there aren't any missing components in your receivers, like the RF filter (can be found near the antenna or ufl). Also check if the SMD antenna is not broken or damaged and it's soldered in properly.
 
 <figure markdown>
-![missing filter](https://cdn.discordapp.com/attachments/899260365555249192/899263539951304714/WhatsApp_Image_2021-07-09_at_1.png)
+![missing filter](../assets/images/missingfilter.png)
 </figure>
 
 - Most DIY modules require moving the 0-ohm resistor on the E28 from the PCB antenna side towards the UFL side. A solder bridge will work just fine as well, but make sure it is on the correct pads.

docs/quick-start/receivers/axisflying-thor.md

@@ -96,7 +96,7 @@ Some of the following procedures will not go through, particularly the via Passt
     8. The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
 
         <figure markdonw>
-        ![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
+        ![LEDSEQ_DISCONNECTED](../../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)
         </figure> 
 
 === "via UART"
@@ -167,7 +167,7 @@ Some of the following procedures will not go through, particularly the via Passt
     11. The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
 
         <figure markdonw>
-        ![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
+        ![LEDSEQ_DISCONNECTED](../../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)
         </figure>
 
 === "via WiFi"
@@ -242,7 +242,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     - The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
 
                     <figure markdown>
-                    ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
+                    ![LEDSEQ_WIFI_UPDATE](../../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
             === "using the ExpressLRS Lua Script" 
@@ -272,7 +272,7 @@ Some of the following procedures will not go through, particularly the via Passt
                 6. The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
 
                     <figure markdown>
-                    ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
+                    ![LEDSEQ_WIFI_UPDATE](../../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
             ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
@@ -319,7 +319,7 @@ Some of the following procedures will not go through, particularly the via Passt
         14. The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
 
             <figure markdonw>
-            ![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
+            ![LEDSEQ_DISCONNECTED](../../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)
             </figure>
 
     === "Manual Upload via Local WiFi"
@@ -386,7 +386,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     - The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
 
                     <figure markdown>
-                    ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
+                    ![LEDSEQ_WIFI_UPDATE](../../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
             === "using the ExpressLRS Lua Script" 
@@ -416,7 +416,7 @@ Some of the following procedures will not go through, particularly the via Passt
                 6. The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
 
                     <figure markdown>
-                    ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
+                    ![LEDSEQ_WIFI_UPDATE](../../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
             ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
@@ -464,7 +464,7 @@ Some of the following procedures will not go through, particularly the via Passt
         13. The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
 
             <figure markdonw>
-            ![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
+            ![LEDSEQ_DISCONNECTED](../../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)
             </figure>
 
     === "Auto Upload"
@@ -492,7 +492,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     - The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
 
                     <figure markdown>
-                    ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
+                    ![LEDSEQ_WIFI_UPDATE](../../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
             === "using the ExpressLRS Lua Script" 
@@ -522,7 +522,7 @@ Some of the following procedures will not go through, particularly the via Passt
                 6. The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
 
                     <figure markdown>
-                    ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
+                    ![LEDSEQ_WIFI_UPDATE](../../assets/images/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
             ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
@@ -570,7 +570,7 @@ Some of the following procedures will not go through, particularly the via Passt
         8. The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
 
             <figure markdonw>
-            ![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
+            ![LEDSEQ_DISCONNECTED](../../assets/images/LEDSEQ_DISCONNECTED_50_50.gif)
             </figure>
 
 [Lua Running]: ../../assets/images/lua/config-bw.png