New updates

docs/about.md

@@ -20,4 +20,4 @@ The rest of the [OARC](https://oarc.uk). Y'all are a consistently fun community
 
 The HAK5 podcast for sparking the first flame and introducing me to APRS and amateur radio way back in 2005/6/7. I have fond memories of hanging out in irc, talking nonsense and taking my first steps into becoming who I am now.
 
-Thanks to those who've come before and wrote the software that I've spent nearly 20 years playing with for fun. The trail you all blazed with your creativity, technical prowess and determination all those years ago has gived many of us years of fun challenges and built a foundation for the future of our hobby. The depth of your understanding and technical ability will never fail to boil my head. Particular thanks to N1URO (now SK), G4KLX, G8PZT and many more at [[insert copyright links for ax25 tools]] who I haven't interacted with directly.
+Thanks to those who've come before and wrote the software that I've spent nearly 20 years playing with for fun. The trail you all blazed with your creativity, technical prowess and determination all those years ago has gived many of us years of fun challenges and built a foundation for the future of our hobby. The depth of your understanding and technical ability will never fail to boil my head. Particular thanks to N1URO (now SK), G4KLX, G8PZT and [many more](https://salsa.debian.org/debian-hamradio-team/ax25-apps/-/blob/master/debian/copyright) who I haven't interacted with directly.

docs/beginners-guide.md

@@ -168,6 +168,7 @@ There are a few great sources of assistance, some will be faster than others to
   * General help and chatter on all things packet: [Online Amateur Radio Club Discord](https://oarc.uk)
   * UK Packet Radio Users: [uk packet radio mailing list](https://groups.io/g/ukpacketradio/)
   * QtTermTCP and QtSoundModem help: [bpq32 mailing list](https://groups.io/g/bpq32/)
-  * NinoTNC: [NinoTNC Mailing List](https://groups.io/g/ninotnc/)
+  * XROUTER help: [XROUTER mailing list](https://groups.io/g/xrouter)
+  * NinoTNC: [NinoTNC mailing list](https://groups.io/g/ninotnc/)
   * My Inbox - see the [about page](about.md). I'll be thrilled if you get stuck and sent me an email saying you'd tried this and nothing worked!
 

docs/index.md

@@ -2,6 +2,10 @@
 
 Hi, welcome - thanks for coming by!
 
+!!! warning
+
+    This is a work in progress. Bits will be missing and added as I have time. If there is anything obviously missing, obviously wrong or that you're in dire need of, drop me an email ([see about page](about.md)) and I'll fix/expedite/help!
+
 ## What is Packet Radio?
 
 Packet Radio is a niche within [Amateur Radio](https://en.wikipedia.org/wiki/Amateur_radio). It combines elements of networking and the dark art of software to connect computers over a long distance without wires.

docs/modems/qtsm.md

@@ -21,7 +21,11 @@ Configuration is done through the menu system.
 
 ### Modem Configuration
 
+Open Settings, then Setup modems, and face this menu:
 
+![config menu](../static/img/qtsm_modem_settings.png)
+
+Select 'IL2P Only' in the IL2P menu, and then run away.
 
 ## Debugging Strategies
 
@@ -64,7 +68,7 @@ Open the input devices tab - does the VU bar of your soundcard show any activity
 
 If you receive a packet and the VU bar goes all the way or is very high, your incoming audio is too high - bring down that slider below the VU bar. If your incoming audio is too high, it might be distorting as the computer digitises it. Having it peak at half way should be more than enough volume.
 
-![receive audio window](static/img/input_devices.png)
+![receive audio window](../static/img/input_devices.png)
 
 This resolves to the following questions:
 
@@ -77,7 +81,7 @@ As in the above segment, open Pulse Audio Volume Control but this time go to the
 
 The VU bar should show activity when a packet is received, just like the one in the Input Devices Tab. If not, you may need to change the device the audio is coming from - there will be a dropdown that lists all your computer's audio inputs and you can select. Again, there is a slider here for volume control - the effects of this are additional to that of the Input Tab, so dropping audio by 6dB in both locations will create a total drop of 12dB. Due to this, I generally recommend leaving it at 100% / 0dB and only modifying the Input Device slider.
 
-[insert image]
+![Incoming Audio](../static/img/recording_dropdown.png)
 
 If you have sorted routing, wait for more packet traffic to see if anything appears in your Terminal monitor pane.
 
@@ -98,13 +102,14 @@ This resolves to the questions:
 
 Open Pulse Audio Volume Control but this time go to the 'Playback' Tab. You should see an entry for QtSoundModem, or Direwolf if that is your poison of choice!
 
-If your modem is not receiving audio, check in the configuration to be sure it is outputting audio to 'Pulse'. In QtSoundModem, this will look as below:
+If your modem is not showing, check in the configuration to be sure it is outputting audio to 'Pulse'. In QtSoundModem, this will look as below:
 
-[insert image]
+![Audio Config](../static/img/qtsm_modem_config.png)
 
-The VU bar should show activity when a packet is transmitted, just like the one in the Input Devices Tab. If not, you may need to change the application volume, and double check the soundcard the application is being sent to. Tere will be a dropdown that lists all your computer's audio inputs and you can select. Again, there is a slider here for volume control - the effects of this are additional to that of the Output Devices Tab, so dropping audio by 6dB in both locations will create a total drop of 12dB. Due to this, I generally recommend leaving it at 100% / 0dB and only modifying the Output Devices slider.
+The VU bar should show activity when a packet is transmitted, just like the one in the Input Devices Tab. If not, you may need to change the application volume, and double check the soundcard the application is being sent to. There will be a dropdown that lists all your computer's audio outputs and you can select. Again, there is a slider here for volume control - the effects of this are additional to that of the Output Devices Tab, so dropping audio by 6dB in both locations will create a total drop of 12dB. Due to this, I generally recommend leaving it at 100% / 0dB and only modifying the Output Devices slider.
 
-[insert image]
+
+![Outgoing Audio](../static/img/playback_dropdown.png)
 
 If you have sorted routing, generate more packet traffic to see if anything appears in your Terminal monitor pane.
 
@@ -120,22 +125,13 @@ This resolves to the questions:
 
 #### Check the audio leaving is at the right volume
 
-!!! note
+Open the Output Devices tab - does the VU bar of your soundcard show any activity? 
 
-    This shall use the Pulse Audio Volume Control program, which is an invaluable friend in wading through Linux audio problems. If it's not obvious where this is in your application launcher, you can open a terminal and type `pavucontrol`. If you don't have it, you should `sudo apt install pavucontrol`.
+If you transmit a packet and the VU bar goes all the way or is very high, your outgoing audio is too high - bring down that slider below the VU bar. If your incoming audio is too high, it might be distorting as the radio modulates it. Having it peak at half way should be more than enough volume. If your radio has an ALC meter, use the slider to set an optimum level in that.
 
-Open the input devices tab - does the VU bar of your soundcard show any activity? In the below screengrab, I have a little audio that is probably just background coming to my Built in soundcard. In many scenarios you'll be using a USB or external soundcard, it might be called a CM108 or similar - be sure you're looking at the right device. Low to no audio as I am showing indicates an issue or an error in the cable. It also might indicate your radio is squelched, be sure to check your squelch is off if possible.
+![Transmit Audio Window](../static/img/output_devices.png)
-
-!!! note
-    If you have no audio coming in and your radio is unsquelched, double check your cable is ok (maybe with a volt meter, or remove and reconnect the ends). Check you are looking at the right soundcard, and check each jack is going to the correct socket on the soundcard.
-
-If you receive a packet and the VU bar goes all the way or is very high, your incoming audio is too high - bring down that slider below the VU bar. If your incoming audio is too high, it might be distorting as the computer digitises it. Having it peak at half way should be more than enough volume.
-
-![receive audio window](static/img/input_devices.png)
 
 This resolves to the following questions:
 
-  * Is the computer receiving audio?
+  * Is the computer generating audio?
-  * Is the received audio too high?
+  * Is the generated audio too high?
-
-