Cleanup and fixes for lmp-testplan page

Language changed to clarify. reference to private repo removed.
Link to release notes folder added, and release notes for v92 and v93
updated to include links to test results.
Other minor fixes to style applied.

QA Steps: ran link check, checked links manually, and
viewed rendered html. Also ran linter. No issues to report.

No related task, quick fix.

Signed-off-by: Katrina Prosise <[email protected]>

release-notes/rn_v92.md

@@ -3,6 +3,7 @@
 > [!NOTE]
 > You can view the full [v92 changelog](https://foundries.io/products/releases/92/) for greater detail.
 
+* [v92 Test Results](https://qa-reports.foundries.io/lmp/lmp-ci-testing/build/51952d1d66536c4432bd3a27f8acbea7bc664f46/)
 
 ## Attention Points for Migration
 

release-notes/rn_v93.md

@@ -3,6 +3,8 @@
 > [!NOTE]
   You can view the full [v93 changelog](https://foundries.io/products/releases/93/) for greater detail.
 
+* [v93 Test Results](https://qa-reports.foundries.io/lmp/lmp-ci-testing/build/90302a18e84910cd360d535bf45ad94eda491954/)
+
 ## Attention Points for Migration
 
 Things to be aware of when [updating LmP](https://docs.foundries.io/93/reference-manual/linux/linux-update.html)from the v92 release:

source/reference-manual/testing/lmp-testplan.rst

@@ -5,28 +5,30 @@ Test Plan
 #########
 
 Below you will find the test plan Foundries.io uses for FoundriesFactory®.
+Test results for each release can be found in the `release notes <https://github.com/foundriesio/docs/tree/main/release-notes>`_.
 
-What To Test
+What to Test
 ============
 
 In the context of this test plan, **mandatory** means the testing that must be performed to release the software.
 Moreover, all tests must pass before the release is announced.
 **Optional** means that the tests may be performed if time allows.
 If optional test results are missing, release can be announced.
 
-Testing must focus on the mandatory features of the FoundriesFactory image:
+Testing focuses on the mandatory features of each FoundriesFactory release:
 
  * Linux microPlatform
  * Base OS running with OSTree based root filesystem
  * Aktualizr-lite daemon
  * Docker engine running Docker compose apps
  * Fioconfig
 
+This includes the open source Linux® microPlatform (LmP) builds on supported SoC vendor reference development evaluation kits (:term:`EVK`).
+
 Remaining elements of the system may be tested as optional but are not as important.
-For example, testing of various I/O interfaces can be done case-by-case depending on the customer requirements and hardware capabilities
+For example, testing of I/O interfaces  done case-by-case depending on customer requirements and hardware capabilities
 
-A complete test list for all devices can be found in the `qa-tools git repository`_.
-Most of the test are stored in the `test-definitions repository`_.
+Most tests are in the `test-definitions repository`_.
 
 LmP Test Plan
 -------------
@@ -229,7 +231,7 @@ We are currently testing 2 scenarios:
    Testing of Docker apps update should be done using a container registered for aktualizr-lite callbacks.
    This way we are as close as possible to testing a production setup.
 
-When To Test
+When to Test
 ============
 
 A testing round is started after every merge to ``lmp-manifest``.
@@ -239,8 +241,5 @@ OTA update is delivered to the *rolling update* devices.
 This also triggers a testing round on the new Target.
 For a release candidate build, additional manual tests are performed.
 
-.. _qa-tools git repository:
-   https://github.com/foundriesio/qa-tools
-
 .. _test-definitions repository:
    https://github.com/linaro/test-definitions