Remove outdated references to past versions

Removed references to versions v91 and prior were appropriate.

This commit applies to issue FFTK-4448, "Review Documentation for v96"

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>

Author: kprosise

source/reference-manual/linux/linux-lmp-fs.rst

@@ -87,7 +87,7 @@ Important Files and Folders
 
 ``/var/sota/sota.toml``: Stores relevant OTA information, like Tag, Apps, custom configurations, certificates location and server address.
 
-``/var/sota/reset-apps``: Holds preloaded apps if :ref:`ug-restorable-apps` are used (default since LmP **v85**).
+``/var/sota/reset-apps``: Holds preloaded apps if :ref:`ug-restorable-apps` are used (default).
 
 ``/var/sota/compose-apps``: Apps are extracted to this location during app loading.
 It holds preloaded apps if Compose Apps are used.

source/reference-manual/linux/linux-oss-compliance.rst

@@ -48,17 +48,17 @@ When using secure boot, the hardware is configured only to execute a complete bo
 
 .. warning:: There are other examples of why a license should be avoided or chosen. Advice from a lawyer is recommended.
 
-.. note:: Another option to meet the GPLv3 requirement when using hardware configured with secure boot,
+.. note::
+   Another option to meet the GPLv3 requirement when using hardware configured with secure boot,
    is providing either a way of disabling secure boot or the keys when requested.
 
-When using LmP there are two variables that can be used for blocking licenses, ``INCOMPATIBLE_LICENSE`` and ``IMAGE_LICENSE_CHECKER_ROOTFS_DENYLIST`` [1]_.
+When using LmP there are two variables that can be used for blocking licenses, ``INCOMPATIBLE_LICENSE`` and ``IMAGE_LICENSE_CHECKER_ROOTFS_DENYLIST``
 Both of these variables list the licenses by SPDX identifier.
 
 INCOMPATIBLE_LICENSE
 """"""""""""""""""""
 
-Add to the ``build/conf/local.conf`` or to the distro the following line [2]_:
-
+Add to the ``build/conf/local.conf`` or to the distro the following line:
 .. code-block:: none
 
    INCOMPATIBLE_LICENSE = "GPL-3.0* LGPL-3.0* AGPL-3.0*"
@@ -90,8 +90,7 @@ Another important difference is that this class prevents the installation of the
 
 This class can be reviewed at `image-license-checker`_.
 
-Add to the LmP Factory customization file ``meta-subscriber-overrides/conf/machine/include/lmp-factory-custom.inc`` the lines from `ci-scripts` [3]_.
-
+Add to the LmP Factory customization file ``meta-subscriber-overrides/conf/machine/include/lmp-factory-custom.inc`` the lines from ``ci-scripts`` [1]_..
 Using this configuration to build ``lmp-factory-image`` results in the following error:
 
 .. code-block:: console
@@ -142,15 +141,7 @@ In this case, the error message guides on which package to target.
 
 .. _image-license-checker: https://github.com/foundriesio/meta-lmp/blob/main/meta-lmp-base/classes/image-license-checker.bbclass
 
-
 .. rubric:: Footnotes
 
-.. [1] Since **v87**,
-       the variable ``IMAGE_LICENSE_CHECKER_ROOTFS_DENYLIST``
-       replaces
-       ``IMAGE_LICENSE_CHECKER_ROOTFS_BLACKLIST``.
-.. [2] Since **v87**,
-     the contents of ``INCOMPATIBLE_LICENSE`` has changed,
-     as a consequence of the Kirkstone SPDX tags change.
-.. [3] The list of license strings follows the SPDX standard and may vary.
+.. [1] The list of license strings follows the SPDX standard and may vary.
        Consult the up-to-date code https://github.com/foundriesio/ci-scripts/blob/master/lmp/bb-config.sh#L189-L192.

source/reference-manual/linux/toolchain.rst

@@ -5,7 +5,7 @@ Toolchain
 
 The default toolchain used in ``openembedded-core`` is ``gcc``, but this is configurable.
 The ``clang`` toolchain is provided by ``meta-clang``, and can be set globally or per recipe.
-Since version **v89**, the LmP uses ``clang`` as the default compiler, and ``llvm`` as the default runtime.
+The LmP uses ``clang`` as the default compiler, and ``llvm`` as the default runtime.
 
 .. code-block::
 

source/reference-manual/security/ff-security-summary.rst

@@ -120,5 +120,3 @@ Additional information can be found in :ref:`ref-ota-security`.
 
 .. note::
    **(*)** Can be selected at Factory creation or changed later.
-
-   Factories created before **v89** use ``RSA 4096`` by default and can switch to use ``Ed25519``.

source/user-guide/containers-and-docker/container-preloading.rst

@@ -55,9 +55,6 @@ making sure to set the appropriate values for ``app_type`` and ``oe_builtin`` (s
   All the  Target's apps are preloaded if not specified or empty.
   Here, it is set to preload the ``shellhttpd`` app.
 - ``app_type`` - Defines the type of Apps to preload.
-  If not defined, or set to an empty value, the ``app_type`` preload will depend on the LmP version.
-  If the LmP version is **v85** or newer, then `restorable` type is preloaded, otherwise `compose` type is used.
-  See :ref:`ug-restorable-apps`.
 - ``oe_builtin`` - *Optional*: Preload Apps during an OE build CI run. Should be left disabled/undefined for most machines.
 
 .. note::
@@ -108,7 +105,7 @@ Checking the Preloaded Image
 Restorable Type
 ~~~~~~~~~~~~~~~
 
-Restorable apps are enabled by default on LmP v85+.
+Restorable apps are enabled by default.
 
 On your device, switch to root and list the files in the folder ``/var/sota/reset-apps``.
 
@@ -141,7 +138,7 @@ Try to start the preloaded Restorable Apps manually using `aklite-apps`:
     # aklite-apps run [--apps <a comma separated list of Apps>]
 
 .. note::
-    ``app_type`` is set to ``restorable`` by default since LmP **v85**.
+    ``app_type`` is set to ``restorable`` by default.
     If ``compose`` app type is set, then the preloaded apps are located under ``/var/sota/compose-apps/<app>``.
     Here is an example using ``shellhttpd`` preloaded app: