Apply suggestions from code review

Co-authored-by: Grzegorz Ferenc <[email protected]>

Author: tomchy

doc/nrf/app_dev/board_names.rst

@@ -46,12 +46,15 @@ While the board name is always present, other elements, such as the board revisi
   Check the Product Specification of the given SoC for more information about the available CPU clusters.
 
 * :ref:`Variant <zephyr:glossary>` - You can use this board qualifier to build for a particular type or configuration of a build for a combination of SoC and CPU cluster.
-  In the |NCS|, variants are used for changing the default memory map as well as indicating the usage of Cortex-M Security Extensions (CMSE) (security by separation):
-
-  * Entry ``nrf52840dongle/nrf52840/bare`` - When you choose this target, the firmware will not account for the onboard USB bootloader (see :ref:`zephyr_board_nrf52840dongle_flashing-option-3` for more details).
-  * Entries without ``*/ns`` (for example, ``cpuapp``) - When you choose this target, you build the application core firmware as a single execution environment that does not use CMSE (:ref:`Trusted Firmware-M (TF-M) <ug_tfm>`).
-  * Entries with ``*/ns`` (for example, ``cpuapp/ns``) - Recommended for more security.
-    When you choose this target, you build the application with CMSE using security by separation.
+  In the |NCS|, variants are used for the following purposes:
+
+  * Changing the default memory map, which applies to the entry for the nRF52840 Dongle with ``*/bare`` (``nrf52840dongle/nrf52840/bare``) - When you choose this target, the firmware will not account for the onboard USB bootloader.
+     This corresponds to using the :ref:`flashing option 3 using an external debug probe <zephyr:nrf52840dongle>` for the dongle.
+  * Indicating the usage of Cortex-M Security Extensions (CMSE) (security by separation):
+    
+    * Entries without ``*/ns`` (for example, ``cpuapp``) - When you choose this target, you build the application core firmware as a single execution environment that does not use CMSE (:ref:`Trusted Firmware-M (TF-M) <ug_tfm>`).
+    * Entries with ``*/ns`` (for example, ``cpuapp/ns``) - Recommended for more security.
+       When you choose this target, you build the application with CMSE using security by separation.
     The application core firmware is placed in Non-Secure Processing Environment (NSPE) and uses Secure Processing Environment (SPE) for security features.
     By default, the build system automatically includes :ref:`Trusted Firmware-M (TF-M) <ug_tfm>` in SPE and merges it with NSPE.
 
@@ -127,7 +130,7 @@ Also see the :ref:`zephyr:boards` section in the Zephyr documentation.
 +-------------------+------------+-----------------------------------------------------+-----------------------------------------------------------------------+
 | nRF52840 Dongle   | PCA10059   | :zephyr:board:`nrf52840dongle <nrf52840dongle>`     | ``nrf52840dongle/nrf52840``                                           |
 |                   |            |                                                     |                                                                       |
-|                   |            |                                                     | ``nrf52840dongle/nrf52840/bare`` (without onboard USB bootloader)     |
+|                   |            |                                                     | ``nrf52840dongle/nrf52840/bare``     |
 +-------------------+------------+-----------------------------------------------------+-----------------------------------------------------------------------+
 | nRF52833 DK       | PCA10100   | :zephyr:board:`nrf52833dk <nrf52833dk>`             | ``nrf52833dk/nrf52833``                                               |
 |                   |            |                                                     |                                                                       |

doc/nrf/includes/sample_board_rows.txt

@@ -16,7 +16,7 @@
 
 .. nrf52840dongle_nrf52840_bare
 
-| nRF52840 Dongle (without onboard USB bootloader) | PCA10059 | :zephyr:board:`nrf52840dongle <nrf52840dongle>` | ``nrf52840dongle/nrf52840/bare`` |
+| nRF52840 Dongle (:ref:`variant without onboard USB bootloader <app_boards>`) | PCA10059 | :zephyr:board:`nrf52840dongle <nrf52840dongle>` | ``nrf52840dongle/nrf52840/bare`` |
 
 .. nrf9160dk_nrf9160
 

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

@@ -307,7 +307,7 @@ nRF Desktop
     Extra ATT buffers are no longer needed for keyboards as :ref:`nrf_desktop_hids` limits the maximum number of simultaneously processed HID input reports (:ref:`CONFIG_DESKTOP_HIDS_SUBSCRIBER_REPORT_MAX <config_desktop_app_options>`) to ``2`` by default.
   * The nRF Desktop application aligns the defaults of :kconfig:option:`CONFIG_BT_ATT_TX_COUNT` and :kconfig:option:`CONFIG_BT_CONN_TX_MAX` Kconfig options to application needs.
     The options are no longer explicitly set in application configurations.
-  * The nRF52840 dongle board target to the ``bare`` varaint to indicate that the application does not use and overwrite the onboard USB bootloader.
+  * The nRF52840 Dongle board target to the ``bare`` variant to indicate that the application does not use and overwrite the onboard USB bootloader.
 
 nRF Machine Learning (Edge Impulse)
 -----------------------------------