Update Flash OS Image and LND Networking pages

Author: tehelsper

docs/.vuepress/public/images/advanced/flash_sd_card_5.png

@@ -1,12 +1,11 @@
-# Flash SD Card Image
+# Flash MyNode OS Image
 
-For many types of devices, including the Raspberry Pi 4, the first step in getting started is to download a MyNode image and flash it onto an SD card. The SD card is then inserted into the device so it can run the MyNode software.
+For most types of devices, including the Raspberry Pi 4 and mini PCs, the first step in getting started is to download a MyNode image and flash it onto a USB flash drive or SD card. The the flash drive is then inserted into the device so it can run the MyNode software.
 
-For some devices, like PCs and laptops, a USB thumbdrive can be used in place of the SD card using the same instructions.
+This same process can be done to load new versions of software, reset your password if it was forgotten, or to swap to a new flash drive with larger storage capacity.
 
-This same process can be done to load new versions of software, reset your password if it was forgotten, or to swap to a new SD card with larger storage capacity.
-
-## What is an SD Card
+<!--
+## What is an SD Card 
 
 The Raspberry Pi and many other devices use a micro SD card that is inserted into a slot in the device. If you need a micro SD card, they will look similar to the image below and can be purchased from [Amazon](https://amzn.to/3x8AI8r).
 
@@ -23,6 +22,7 @@ On the Raspberry Pi, the SD card slot can be found on the bottom of the device.
     <img src="/images/advanced/flash_sd_card_3.png" width="300">
   </figure>
 </center>
+-->
 
 ## Download the Software Image
 
@@ -34,21 +34,15 @@ You will need to download the image for your device from [mynodebtc.com/download
   </figure>
 </center>
 
-Once downloaded, the software needs to be written to the SD card.
-
-## Flash SD Card
+Once downloaded, the software needs to be written to the flash drive.
 
-To load software image on the SD card, you will need a way to connect the SD card to your computer. Some PCs and laptops have a slot to insert them, but most users will need a USB to micro SD adapter. They can be found on [Amazon](https://amzn.to/38OtQF4).
+## Flash the OS Image
 
-<center>
-  <figure>
-    <img src="/images/advanced/flash_sd_card_4.png" width="200">
-  </figure>
-</center>
+To load software image on the USB drive or SD card, you will need to connect it to your computer. If you have an SD card, you will need a way to connect it to your computer. Some PCs and laptops have a slot to insert them, but most users will need a USB to micro SD adapter. They can be found on [Amazon](https://amzn.to/38OtQF4).
 
-Put the SD card into the adapter and connect it to your PC.
+Connect the flash drive to your computer.
 
-Then, download [Etcher](https://www.balena.io/etcher/), a program for writing software images to SD cards, and install it on your PC or Mac.
+Then, download [Etcher](https://www.balena.io/etcher/), a program for writing software images, and install it on your PC or Mac.
 
 Open Etcher and click "Flash from file" and choose the recently downloaded image.
 
@@ -82,7 +76,7 @@ Once selected, click "Flash!" and the image will be written to the drive. The fl
   </figure>
 </center>
 
-Once the image has been flashed to the SD card, you can remove it from the PC.
+Once the image has been written to the flash drive, you can remove it from the PC.
 
 <center>
   <figure>
@@ -91,9 +85,9 @@ Once the image has been flashed to the SD card, you can remove it from the PC.
 </center>
 
 
-## Insert SD Card into Device
+## Insert Flash Drive into Device
 
-Finally, the last step is to take the SD card and insert it into the unpowered device.
+Finally, the last step is to take the flash drive and insert it into the unpowered device.
 
 <center>
   <figure>

docs/advanced/flash-sd-card.md

@@ -10,24 +10,28 @@ To confirm you are having this issue, find the Lightning log on the status page
 Jan 12 14:57:21 mynode lnd[15786]: unable to create server: unable to discover a NAT-PMP enabled device on the local network
 ```
 
-This is caused by your network config being set to use Clearnet for Lightning. The Lightning daemon is attempting to communicate with your router to open a port and is failing. Disabling Clearnet setting will resolve the issue.
+This is caused by your network config being set to use Clearnet for Lightning. The Lightning daemon is attempting to communicate with your router to open a port and is failing. You can disable Clearnet or customize your config to resolve this issue.
 
-If you router has public IP address and you are skilled and able to configure port forwarding there might be resolution for advanced users to able to continue using clearnet. 
+If you router has public IP address and you are skilled and able to configure port forwarding, you can edit your Lightning config to resolve the issue and continue using Clearnet. 
 
-## Resolution
+## Simple Resolution - Enable Tor
 
 First, go to the main settings page on your node and scroll to the "Networking" section. In the row for Lightning, disable Clearnet and enable Tor. Save the config. Your device will reboot and Lightning should start as expected.
 
 If you are still having issues, that setting may not have taken effect because of a [custom Lightning config](/advanced/customize-config.md). Reset your custom Lightning config back to the default so the network settings can take effect.
 
-## Advanced User Resolution
+<br/>
+<details>
+<summary><b>Show Advanced Resolutions</b></summary>
 
-As UPnP is not working Advanced Resolution requires user to manually configure port forwarding to router / firewall device and add required parameters to Additional LND Config on MyNode. Even with this case, it may not work due some ISP's do not provide your router real public IP address.
+## Advanced Resolution - Custom Config with Static Public IP
 
-Configure onto modem/router/firewall portforwarding from any public IP address to routers public TCP port 9735 to you MyNode private network IP address port 9735.
+As UPnP is not working, another option is to configure port forwarding on your router / firewall device and add required parameters to Additional LND Config on MyNode. This is not guaranteed to work and is not supported by some ISPs as they do not provide your router a real public IP address.
+
+Configure your modem/router/firewall to enable port forwarding from your public IP address TCP port 9735 to you MyNode device's IP address port 9735.
 
 Go to MyNode main settings page. Find "Lightning" below it click "Edit Config" and "LND Custom Config" page opens. 
-Onto "Additional LND Config" text box enter configuration lines:
+In the "Additional LND Config" text box enter configuration lines:
 ```
 # Nonworking UPnP Router fix
 nat=false
@@ -36,21 +40,23 @@ nat=false
 externalhosts=<YOUR-EXTERNAL-IP>:9735
 ```
 
-As usually public IP addresses of home Internet connections are not static, and therefore change once a while. So this solution is acceptible _only if you have _real_ static IP_ from your ISP (or cloud) provider.
+Usually, the public IP addresses of home Internet connections are not static, and therefore change once a while. So this solution is acceptible _only if you have _real_ static IP_ from your ISP (or cloud) provider.
+
+## Advanced Resolution - Custom Config with Dynamic Public IP
 
-Internet connections with Dynamic Public IP addresses require bit more configurations. 
+Internet connections with Dynamic Public IP addresses require bit more configuration. 
 
 Dynamic DNS must be implemented and DNS hostname must be configured to Additional LND Config.
 
-Dynamic DNS (DDNS) hostname can be created free by opening account to eg. www.no-ip.com, but free DDNS hostnames must be re-verified every 30 days or so. Let's say you make account and create DDNS hostname "mymynodebtc.ddns.net".
+Dynamic DNS (DDNS) hostname can be created for free by opening account to eg. www.no-ip.com, but free DDNS hostnames must be re-verified every 30 days or so. These will give you a domain name to use in place of your public IP since it may change. Let's say you make account and create DDNS hostname "mymynodebtc.ddns.net".
 
 To keep DDNS hostname's IP address updated in case of IPS changes your address, you need to do one of following.
 
-a) Install and configure DDNS Client software to your MyNode (eg. https://www.noip.com/download?page=linux ) and verify it's proper functioning.
+a) Install and configure DDNS Client software to your MyNode (eg. https://www.noip.com/download?page=linux) and verify it is working properly.
 
-b) Configure DDNS Service onto your Modem/Router/Firewall if it supports such function (eg. some Sagemcom cable modems do support).
+b) Enable and configure DDNS Service on your Modem/Router/Firewall if it supports such functionality.
 
-After these are done, you can add following lines in your Additional LND Config (do not include one line with IP Address shown above!)
+After the DDNS software is configured and running, you can add following lines in your Additional LND Config (do not include the line with IP Address shown in the previous section).
 ```
 # Nonworking UPnP Router fix
 nat=false
@@ -60,17 +66,19 @@ tlsextradomain=mymynodebtc.ddns.net
 externalhosts=mymynodebtc.ddns.net:9735
 ```
 
-Naturally use your own DDNS hostname instead of this sample one. Press Save and you MyNode will reboot with new settings.
+Be sure to use your own DDNS hostname instead of this sample one. Press Save and your MyNode will reboot with new settings.
 
-From MyNode Main page click Lightning - Wallet. Notice on "URI" you have your node long ID followed by your IP address:9735 shown! This means successful configuration. Now click TLS Certificates button _regenerate_. After regeneration is complete in a monent, click download and save certificate (on Windows machine) as tls.crt (not .cert!). Open .crt file and verify from Details tab field "Subject Alternative Name". Your DDNS hostname must included on the DNS Name= ... list.
+From the MyNode Main page, click Lightning - Wallet. Notice on "URI" you have your node long ID followed by your IP address:9735 shown! This means the configuration was successful. Now, click TLS Certificates button _regenerate_. After regeneration is complete, click download and save certificate (on Windows machine) as tls.crt (not .cert!). Open .crt file and verify from Details tab field "Subject Alternative Name". Your DDNS hostname must included on the DNS Name= ... list.
 
 Now your LND is able to receive channels from clearnet.
 
-If you own the domain (say mydomain.com) you can add CNAME for DDNS address alias onto you domain DNS records like this:
+## Advanced Resolution - Custom Config with Dynamic Public IP and Domain
+
+If you own the domain (say mydomain.com) you can add a CNAME for your DDNS address alias in your domain DNS records like this:
 
 ```myownnode IN CNAME mymynodebtc.ddns.net.```
 
-Add this new hostname with additional tlsextradomain to config. In such more Advanced case config would be now
+Add this new hostname with additional tlsextradomain to config. In this more advanced case, the config would now be:
 ```
 # Nonworking UPnP Router fix
 nat=false
@@ -80,13 +88,14 @@ tlsextradomain=myownnode.mydomain.com
 tlsextradomain=mymynodebtc.ddns.net
 externalhosts=mymynodebtc.ddns.net:9735
 ```
-Recreate TLS certs, download and verify DNS Name= list from cert. 
-Now your node can be connected with short address:
+
+Re-create TLS certs, download and verify DNS Name= list from cert. 
+Now your node can be connected with the short address:
 
 ```https://myownnode.mydomain.com:9735```
 
-And address will work even you ISP causes address changes.
+Now, this address will work even if your ISP changes your public IP.
 
-If you now plan to provide BTCPay Server or LNbits onto clearnet - you are not quite done yet. BTCPay and LNbits require https traffic to public TCP port 443 and non-selfsigned TSL certificates. Such certs be created with Linux with certbot installed on MyNode. HTTPS traffic inside of MyNode can be forwared with nginx configs, but those configurations are out of scope for this guide.
+If you now plan to provide BTCPay Server or LNbits via clearnet - you are not quite done yet. BTCPay and LNbits require https traffic to public TCP port 443 and non-selfsigned TLS certificates. Such certs be created with Linux with certbot installed on MyNode. HTTPS traffic inside of MyNode can be forwared with nginx configs, but those configurations are out of scope for this guide.
 
-Advanced User Resolution ends here. (So normal Resolution is a bit more simple.)
+</details>