applications: nrf_desktop: Small documentation alignments

Changes align documentation with code. Change also adds a link to
Fast Pair software maturity.

Jira: NCSDK-30908

Signed-off-by: Marek Pieta <[email protected]>

Author: MarekPieta

applications/nrf_desktop/bluetooth.rst

@@ -171,10 +171,7 @@ The nRF Desktop peripheral can be built with Google `Fast Pair`_ support.
 The configurations that enable Fast Pair are specified in the files with filenames ending with the ``fast_pair`` and ``release_fast_pair`` suffixes.
 
 .. note::
-   The Fast Pair integration in the nRF Desktop is :ref:`experimental <software_maturity>`.
-   The factory reset of the Fast Pair non-volatile data is not yet supported.
-
-   The Fast Pair support in the |NCS| is :ref:`experimental <software_maturity>`.
+   Both the Fast Pair integration in the nRF Desktop and the Fast Pair support in the |NCS| for the HID use case are :ref:`experimental <software_maturity_fast_pair>`.
    See :ref:`ug_bt_fast_pair` for details.
 
 These configurations support multiple bonds for each Bluetooth local identity (:kconfig:option:`CONFIG_CAF_BLE_STATE_MAX_LOCAL_ID_BONDS` is set to ``3``) and erase advertising (:ref:`CONFIG_DESKTOP_BLE_PEER_ERASE <config_desktop_app_options>`), but Bluetooth peer selection (:ref:`CONFIG_DESKTOP_BLE_PEER_SELECT <config_desktop_app_options>`) is disabled.

applications/nrf_desktop/bootloader_dfu.rst

@@ -7,7 +7,7 @@ nRF Desktop: Bootloader and Device Firmware Update
    :local:
    :depth: 2
 
-The nRF Desktop application uses the :ref:`bootloaders <app_bootloaders>` firmware image that allows you to upgrade the used application firmware image using the :ref:`app_dfu` procedure.
+The nRF Desktop application uses the :ref:`bootloaders <app_bootloaders>` firmware image that allows you to upgrade the used application firmware image using either the :ref:`app_dfu` procedure or :ref:`ug_nrf54h20_suit_dfu`.
 
 You can use the following Device Firmware Update (DFU) procedures for upgrading the application firmware version:
 
@@ -238,7 +238,7 @@ SUIT also has the following options in the sysbuild configuration:
 .. note::
    The ``SB_CONFIG_SUIT_ENVELOPE_SIGN`` is disabled, so the generated SUIT envelope is not signed.
 
-By default, the SUIT generator sets the values inside the manifest based on the content of the :file:`VERSION` file, used for :ref:`zephyr:app-version-details` in Zephyr and the |NCS|.:
+By default, the SUIT generator sets the values inside the manifest based on the content of the :file:`VERSION` file, used for :ref:`zephyr:app-version-details` in Zephyr and the |NCS|:
 
    * The manifest sequence number is set in the same manner as the ``APPVERSION`` CMake variable.
    * The manifest current (semantic) version is set in the same manner as the ``APP_VERSION_EXTENDED_STRING`` CMake variable.

applications/nrf_desktop/memory_layout.rst

@@ -29,8 +29,6 @@ By default, a Zephyr-based application defines the memory layout in the DTS.
 If enabled, the :ref:`partition_manager` defines a new memory layout that is used instead of the memory layout defined in the DTS.
 You can use the :kconfig:option:`CONFIG_PARTITION_MANAGER_ENABLED` Kconfig option value to check whether the Partition Manager is enabled in the current build.
 The option is automatically enabled when using Zephyr's :ref:`zephyr:sysbuild` (unless your board uses nRF54H SoC Series).
-Enabling the :ref:`nrf_desktop_bluetooth_guide_fast_pair` also results in using the Partition Manager.
-To store the Fast Pair Provisioning data, the Fast Pair integration in the |NCS| uses partition defined by the Partition Manager.
 
 Memory layout in DTS
 ********************
@@ -40,7 +38,7 @@ For example, the nRF52 Series devices use non-volatile flash memory represented
 Make sure to also update the DTS chosen nodes, which represent the code partition (``zephyr,code-partition``) and flash (``zephyr,flash``), if needed.
 
 If you wish to change the default memory layout of the board without editing the board-specific files, edit the DTS overlay file.
-The nRF Desktop application automatically adds the :file:`dts.overlay` file if it is present in the project's board configuration directory.
+The nRF Desktop application automatically adds the :file:`app.overlay` file if it is present in the project's board configuration directory.
 For more details, see the :ref:`nrf_desktop_board_configuration` section.
 
 .. important::

doc/nrf/releases_and_maturity/software_maturity.rst

@@ -1736,6 +1736,8 @@ The following sections contain the tables indicating the software maturity level
 
 * Google Fast Pair
 
+.. _software_maturity_fast_pair:
+
 Google Fast Pair
 ================