change nightly build filename text (#254)

aredn · May 6, 2023 · 3e096a4 · 3e096a4
1 parent 19ef24a
commit 3e096a4
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/arednGettingStarted/downloading_firmware.rst b/arednGettingStarted/downloading_firmware.rst
@@ -7,7 +7,7 @@ Types of Firmware
 
 **Stable Release** firmware has been tested and shown work on the devices that were supported at the time of the release. This firmware is considered to be stable and suitable for production devices deployed in the field. Stable Release firmware is identified by numbers such as ``3.23.4.0``. In this example ``23.4`` indicates the year (2023) and month (April) of the Stable Release.
 
-**Nightly Build** firmware contains the latest bug fixes, features, and support for new devices. It allows the wider mesh community to test new code before it is included in a Stable Release. The Nightly Build is considered more experimental or cutting-edge and may not be suitable for production nodes. However, it might make sense to install the Nightly Build if you are having a specific issue that has been addressed in newly developed code or if you are loading AREDN |trade| firmware onto a device that is newly supported. The Nightly Build firmware will have a series of alphanumeric characters such as ``2526-e8911a9`` indicating the software commit identifier for that specific firmware build.
+**Nightly Build** firmware contains the latest bug fixes, features, and support for new devices. It allows the wider mesh community to test new code before it is included in a Stable Release. The Nightly Build is considered more experimental or cutting-edge and may not be suitable for production nodes. However, it might make sense to install the Nightly Build if you are having a specific issue that has been addressed in newly developed code or if you are loading AREDN |trade| firmware onto a device that is newly supported. The Nightly Build filename shows the build date and the software commit identifier for that specific firmware build.
 
 Choosing Firmware to Download
 -----------------------------
@@ -47,6 +47,6 @@ Features Inherited from OpenWRT for New Architectures
   All supported devices have been migrated to the new targets. **You should select the latest recommended target image based on the type of hardware on which it will be installed.** Refer to the latest `Supported Devices <http://downloads.arednmesh.org/snapshots/SUPPORTED_DEVICES.md>`_ in order to ensure you have the correct firmware image for your specific device.
 
 Nightly Build Direct Download
-  To download the *Nightly Build* directly, navigate to `http://downloads.arednmesh.org/snapshots/targets/ <http://downloads.arednmesh.org/snapshots/targets/>`_. Nightly Build filenames are prefixed with *aredn-XXXX-yyyyyyy*, where *XXXX* identifies the build number and *yyyyyyy* is a unique software commit identifier. As explained above, select the correct target and subtarget for the device you will be flashing. To return your device to the current stable release, download the correct *Stable Release* firmware and reflash your device.
+  To download the *Nightly Build* directly, navigate to `http://downloads.arednmesh.org/snapshots/targets/ <http://downloads.arednmesh.org/snapshots/targets/>`_. Nightly Build filenames are prefixed with the firmware build date and a unique software commit identifier. As explained above, select the correct target and subtarget for the device you will be flashing. To return your device to the current stable release, download the correct *Stable Release* firmware and reflash your device.
 
   Be aware that when a new nightly build becomes available, any older builds automatically become obsolete. If you want to install add-on packages for nodes running a nightly build, understand that specific packages will not be available for an *older* build if a *newer* build has superseded it. Be sure to upgrade to the current nightly build before installing packages.
diff --git a/arednHow-toGuides/lqm.rst b/arednHow-toGuides/lqm.rst
@@ -60,7 +60,7 @@ AREDN |trade| is an open, ad hoc, network allowing any node to associate with an
 Link Quality Manager (LQM)
 --------------------------
 
-The *Link Quality Manager* can be enabled on any node running the current nightly build or newer firmware. It runs in the background to evaluate RF links and automatically take the following actions: 
+The *Link Quality Manager* can be enabled on any node running 3.22.12.0 or newer firmware. It runs in the background to evaluate RF links and automatically take the following actions: 
 
 1. Blocks radio links which are also DtD links
 2. Blocks radio links which have too low an SNR