doc: wayland: update desktop app names

Updated nRF Connect for Desktop app names to match the application.
Dropped `nRF Connect` from the name and added `app` after.
Reasons in NCD-1066.

Signed-off-by: Grzegorz Ferenc <[email protected]>

Author: greg-fer

applications/asset_tracker_v2/doc/asset_tracker_v2_description.rst

@@ -180,9 +180,9 @@ Testing
 After programming the application and all the prerequisites to your development kit, test the application by performing the following steps:
 
 1. |connect_kit|
-#. Connect to the kit with a terminal emulator (for example, `nRF Connect Serial Terminal`_).
-   You can also use the :guilabel:`Open Serial Terminal` option of the `Cellular Monitor`_ app to open the Serial Terminal.
-   Using the Cellular Monitor app in combination with the nRF Connect Serial Terminal shows how the modem responds to the different modem commands.
+#. Connect to the kit with a terminal emulator (for example, the `Serial Terminal app`_).
+   You can also use the :guilabel:`Open Serial Terminal` option of the `Cellular Monitor app`_ to open the Serial Terminal app.
+   Using the Cellular Monitor app in combination with the Serial Terminal app shows how the modem responds to the different modem commands.
 #. Reset the development kit.
 #. Observe in the terminal window that application boots as shown in the following output::
 

applications/machine_learning/app_desc.rst

@@ -539,7 +539,7 @@ After programming the application, perform the following steps to test the nRF M
    After a brief delay, the Bluetooth connection between the sample and the Thingy is established.
    The Thingy forwards the sensor readouts over NUS.
    The LED on the Thingy starts to blink rapidly.
-#. Connect to the sample with a terminal emulator (for example, `nRF Connect Serial Terminal`_).
+#. Connect to the sample with a terminal emulator (for example, the `Serial Terminal app`_).
    See :ref:`test_and_optimize` for the required settings.
 #. Observe the sensor readouts represented as comma-separated values.
    Every line represents a single sensor readout.
@@ -568,7 +568,7 @@ After programming the application, perform the following steps to test the nRF M
    This signal is marked as an anomaly by the machine learning model, and **LED1** starts breathing.
 #. Press and hold **Button 1** for more than five seconds to switch to the data forwarding mode.
    After the mode is switched, **LED1** starts to blink rapidly.
-#. Connect to the development kit with a terminal emulator (for example, `nRF Connect Serial Terminal`_).
+#. Connect to the development kit with a terminal emulator (for example, the `Serial Terminal app`_).
    See :ref:`test_and_optimize` for the required settings.
 #. Observe the sensor readouts represented as comma-separated values.
    Every line represents a single sensor readout.
@@ -595,7 +595,7 @@ After programming the application, perform the following steps to test the nRF M
    This signal is marked as an anomaly by the machine learning model, and **LED1** starts breathing.
 #. Press and hold **Button 0** for more than five seconds to switch to the data forwarding mode.
    After the mode is switched, **LED1** starts to blink rapidly.
-#. Connect to the development kit with a terminal emulator (for example, `nRF Connect Serial Terminal`_).
+#. Connect to the development kit with a terminal emulator (for example, the `Serial Terminal app`_).
    See :ref:`test_and_optimize` for the required settings.
 #. Observe the sensor readouts represented as comma-separated values.
    Every line represents a single sensor readout.

applications/serial_lte_modem/doc/slm_description.rst

@@ -407,18 +407,18 @@ To connect to an nRF91 Series DK with a PC:
 1. Verify that ``UART_0`` is selected in the application.
    It is defined in the default configuration.
 
-2. Use `nRF Connect Serial Terminal`_ to connect to the development kit.
+2. Use the `Serial Terminal app`_ to connect to the development kit.
    See :ref:`serial_terminal_connect` for instructions.
-   You can also use the :guilabel:`Open Serial Terminal` option of the `Cellular Monitor`_ app to open the Serial Terminal.
-   Using the Cellular Monitor app in combination with the nRF Connect Serial Terminal shows how the modem responds to the different modem commands.
+   You can also use the :guilabel:`Open Serial Terminal` option of the `Cellular Monitor app`_ to open the Serial Terminal app.
+   Using the Cellular Monitor app in combination with the Serial Terminal app shows how the modem responds to the different modem commands.
    You can then use this connection to send or receive AT commands over UART, and to see the log output of the development kit.
 
-   Instead of using nRF Connect Serial Terminal, you can use PuTTY to establish a terminal connection to the development kit, using the :ref:`default serial port connection settings <test_and_optimize>`.
+   Instead of using the Serial Terminal app, you can use PuTTY to establish a terminal connection to the development kit, using the :ref:`default serial port connection settings <test_and_optimize>`.
 
    .. note::
 
       The default AT command terminator is a carriage return followed by a line feed (``\r\n``).
-      nRF Connect Serial Terminal supports this format.
+      The Serial Terminal app supports this format.
       If you want to use another terminal emulator, make sure that the configured AT command terminator corresponds to the line terminator of your terminal.
       When using PuTTY, you must set the :ref:`CONFIG_SLM_CR_TERMINATION <CONFIG_SLM_CR_TERMINATION>` SLM configuration option.
       See :ref:`slm_config_options` for more details.
@@ -642,8 +642,8 @@ If you have an nRF52 Series DK running a client application, you can also use th
 |test_sample|
 
 1. |connect_kit|
-#. :ref:`Connect to the kit with nRF Connect Serial Terminal <serial_terminal_connect>`.
-   You can also use the :guilabel:`Open Serial Terminal` option of the `Cellular Monitor`_ app to open the Serial Terminal.
+#. :ref:`Connect to the kit with the Serial Terminal app <serial_terminal_connect>`.
+   You can also use the :guilabel:`Open Serial Terminal` option of the `Cellular Monitor app`_ to open the Serial Terminal app.
    If you want to use a different terminal emulator, see :ref:`slm_connecting_91dk_pc`.
 #. Reset the kit.
 #. Observe that the development kit sends a ``Ready\r\n`` message on UART.

applications/serial_lte_modem/doc/slm_testing.rst

@@ -377,8 +377,8 @@ TLS client
 Before completing this test, you must update the CA certificate, the client certificate, and the private key to be used for the TLS connection in the modem.
 The credentials must use the security tag 16842755.
 
-To store the credentials in the modem, use the Cellular Monitor app.
-See `Managing credentials`_ in the Cellular Monitor User Guide for instructions.
+To store the credentials in the modem, use the `Cellular Monitor app`_.
+See `Managing credentials`_ in the Cellular Monitor app documentation for instructions.
 
 You must register the corresponding credentials on the server side.
 

doc/nrf/app_dev/device_guides/nrf52/features.rst

@@ -10,7 +10,7 @@ Features of nRF52 Series
 The nRF52 Series of System-on-Chip (SoC) devices embed an Arm Cortex-M4 processor with Nordic Semiconductor's 2.4 GHz RF transceivers.
 All of the nRF52 Series SoCs have support for Bluetooth® 5 features, in addition to multiprotocol capabilities.
 
-To get started with the nRF52 Series, download and run the `Quick Start`_ application from `nRF Connect for Desktop`_.
+To get started with the nRF52 Series, download and run the `Quick Start app`_ in `nRF Connect for Desktop`_.
 
 For additional information, see the following documentation:
 

doc/nrf/app_dev/device_guides/nrf53/features_nrf53.rst

@@ -10,7 +10,7 @@ Features of nRF53 Series
 The nRF53 Series System-on-Chips (SoC) integrate a high-performance Arm® Cortex®-M33 dual-core processor with a 2.4 GHz RF transceiver, in addition to advanced security features.
 All nRF53 Series SoC support Bluetooth® 5.1 and Bluetooth Mesh, in addition to multiprotocol capabilities.
 
-To get started with the nRF5340 DK, download and run the `Quick Start`_ application from `nRF Connect for Desktop`_.
+To get started with the nRF5340 DK, download and run the `Quick Start app`_ in `nRF Connect for Desktop`_.
 
 For additional information, refer to the following resources:
 

doc/nrf/app_dev/device_guides/nrf53/thingy53_application_guide.rst

@@ -28,7 +28,7 @@ Updating firmware image for Thingy:53
 *************************************
 
 You can program the firmware on the Nordic Thingy:53 using an external debug probe and 10-pin JTAG cable, as described in :ref:`thingy53_building_pgming`, using either :ref:`Visual Studio Code <thingy53_build_pgm_vscode>` or :ref:`command line <thingy53_build_pgm_command_line>`.
-You can also update applications running on both the network and application core using the built-in MCUboot bootloader and `nRF Connect Programmer`_ or the `nRF Programmer`_ app for Android and iOS.
+You can also update applications running on both the network and application core using the built-in MCUboot bootloader and the `Programmer app`_ for desktop or the `nRF Programmer`_ app for Android and iOS.
 You can also update the prebuilt application images that way.
 
 See :ref:`thingy53_gs_updating_firmware` for details about updating firmware image.
@@ -54,7 +54,7 @@ You can program the precompiled firmware image using one of the following ways:
   In this scenario, the Thingy is connected directly to your PC through USB.
   For details, refer to the :ref:`thingy53_app_mcuboot_bootloader` section.
 
-  See the :ref:`thingy53_gs_updating_usb` section in the :ref:`ug_thingy53_gs` guide for the detailed procedures on how to program the Thingy:53 using `nRF Connect Programmer`_.
+  See the :ref:`thingy53_gs_updating_usb` section in the :ref:`ug_thingy53_gs` guide for the detailed procedures on how to program the Thingy:53 using the `Programmer app`_.
 * Update the firmware over-the-air (OTA) using Bluetooth LE and the nRF Programmer mobile application for Android or iOS.
   To use this method, the application that is currently programmed on Thingy:53 must support it.
   For details, refer to :ref:`thingy53_app_fota_smp` section.

doc/nrf/app_dev/device_guides/nrf70/index.rst

@@ -35,28 +35,28 @@ Zephyr and the |NCS| provide support for developing networking applications with
      - PCA10095
      - ``nrf5340dk/nrf5340/cpuapp``
      - | `Product Specification <nRF5340 Product Specification_>`_
-       | `Quick Start`_
+       | `Quick Start app`_
        | `User Guide <nRF5340 DK User Guide_>`_
    * - :ref:`zephyr:nrf52840dk_nrf52840`
      - nRF7002 EK
      - PCA10056
      - ``nrf52840dk/nrf52840``
      - | `Product Specification <nRF52840 Product Specification_>`_
-       | `Quick Start`_
+       | `Quick Start app`_
        | `User Guide <nRF52840 DK User Guide_>`_
    * - :ref:`zephyr:nrf9151dk_nrf9151`
      - nRF7002 EK
      - PCA10171
      - ``nrf9151dk/nrf9151/ns``
      - | `Product Specification <nRF9151 Product Specification_>`_
-       | `Quick Start`_
+       | `Quick Start app`_
        | `User Guide <nRF9151 DK Hardware_>`_
    * - :ref:`zephyr:nrf9161dk_nrf9161`
      - nRF7002 EK
      - PCA10153
      - ``nrf9161dk/nrf9161/ns``
      - | `Product Specification <nRF9161 Product Specification_>`_
-       | `Quick Start`_
+       | `Quick Start app`_
        | `User Guide <nRF9161 DK Hardware_>`_
    * - :ref:`zephyr:nrf9160dk_nrf9160`
      - nRF7002 EK
@@ -81,7 +81,7 @@ Zephyr and the |NCS| provide support for developing networking applications with
      - nRF7002 EB
      - PCA20053
      - ``nrf54l15dk/nrf54l15/cpuapp``
-     - | `Quick Start`_
+     - | `Quick Start app`_
        | :ref:`Developing with nRF54L Series <ug_nrf54l15_gs>`
 
 

doc/nrf/app_dev/device_guides/nrf91/index.rst

@@ -25,7 +25,7 @@ Zephyr and the |NCS| provide support for developing cellular applications using
      - PCA10153
      - ``nrf9161dk/nrf9161``, ``nrf9161dk/nrf9161/ns``
      - | `Product Specification <nRF9161 Product Specification_>`_
-       | `Quick Start`_
+       | `Quick Start app`_
        | `User Guide <nRF9161 DK Hardware_>`_
      - | `nRF9161 DK product page`_
        | `nRF9161 System in Package (SiP) <nRF9161 product website_>`_
@@ -41,7 +41,7 @@ Zephyr and the |NCS| provide support for developing cellular applications using
      - PCA10171
      - ``nrf9151dk/nrf9151``, ``nrf9151dk/nrf9151/ns``
      - | `Product Specification <nRF9151 Product Specification_>`_
-       | `Quick Start`_
+       | `Quick Start app`_
        | `User Guide <nRF9151 DK Hardware_>`_
      - | `nRF9151 DK product page`_
        | `nRF9151 System in Package (SiP) <nRF9151 product website_>`_

doc/nrf/app_dev/device_guides/nrf91/nrf91_board_controllers.rst

@@ -23,7 +23,7 @@ The following sections have a complete list of configuration options available f
 * `Board control <nRF9151 DK board control section in the nRF9151 DK User Guide_>`_  in the nRF9151 DK Hardware guide
 
 The nRF5340 IMCU comes preprogrammed with J-Link SEGGER OB and board controller firmware.
-If you want to change the default configuration of the DK, you can use the `nRF Connect Board Configurator`_ app in `nRF Connect for Desktop`_ .
+If you want to change the default configuration of the DK, you can use the `Board Configurator app`_ in `nRF Connect for Desktop`_ .
 
 To update board controller firmware on the nRF9161 DK, download the `nRF9161 DK board controller firmware`_ from the nRF9161 DK downloads page.
 To program the HEX file, use `nRF Util`_.