doc: add registered trademark to Bluetooth mentions

Add several registered trademark symbols to the documentation.
This is to align with the official Bluetooth branding guidelines.
Also some small text fixes to the affected files.
JIRA: https://projecttools.nordicsemi.no/jira/browse/NCSDK-10721

Signed-off-by: Wille Backman <[email protected]>

Author: wiba-nordic

applications/connectivity_bridge/README.rst

@@ -9,7 +9,7 @@ Connectivity bridge
 
 The Connectivity bridge application demonstrates the bridge functionality for the Thingy:91 hardware.
 
-Additionally, the application also provides an option of adding the bluetooth functionality by making use of the :ref:`nus_service_readme`.
+Additionally, the application also provides an option of adding the Bluetooth® functionality by making use of the :ref:`nus_service_readme`.
 
 Overview
 ********
@@ -32,7 +32,7 @@ See :ref:`thingy91_serialports` for information on the baud rate configuration f
 
 The application adds the functionality of a USB Mass Storage device, which contains several utility files such as a :file:`README.txt` file.
 
-The application also provides a Bluetooth LE UART Service, which can be enabled by the option ``CONFIG_BRIDGE_BLE_ENABLE``.
+The application also provides a Bluetooth® LE UART Service, which can be enabled by the option ``CONFIG_BRIDGE_BLE_ENABLE``.
 This service can be used for a wireless connection to one of the UART interfaces in the following way:
 
 .. list-table::

applications/machine_learning/README.rst

@@ -89,7 +89,7 @@ The figure visualizes relations between Event Manager, modules, drivers, and lib
 
 Since the application architecture is uniform and the code is shared, the set of modules in use depends on configuration.
 In other words, not all of the modules need to be enabled for a given reference design.
-For example, the :ref:`caf_ble_state` and :ref:`caf_ble_adv` modules are not enabled if the configuration does not use Bluetooth.
+For example, the :ref:`caf_ble_state` and :ref:`caf_ble_adv` modules are not enabled if the configuration does not use Bluetooth®.
 
 See :ref:`nrf_machine_learning_app_internal_modules` for detailed information about every module used by the nRF Machine Learning application.
 
@@ -348,10 +348,10 @@ After programming the application, perform the following steps to test the nRF M
    After the mode is switched, the LED color changes to red and the LED starts blinking very slowly.
 #. Program the :ref:`central_uart` sample to a compatible development kit, for example the nRF52840 Development Kit.
    Turn on the programmed device.
-   After a brief delay the Bluetooth connection between the sample and the Thingy:52 is established.
+   After a brief delay the Bluetooth® connection between the sample and the Thingy:52 is established.
    The Thingy:52 forwards the sensor readouts over NUS.
    The LED on the Thingy:52 starts to blink rapidly.
-#. Connect to the Bluetooth Central UART sample with a terminal emulator (for example, PuTTY).
+#. Connect to the Bluetooth® Central UART sample with a terminal emulator (for example, PuTTY).
    See :ref:`putty` for the required settings.
 #. Observe the sensor readouts represented as comma-separated values.
    Every line represents a single sensor readout.

applications/matter_weather_station/README.rst

@@ -42,7 +42,7 @@ The measurement results are stored in the device memory and can be read using th
 The controller communicates with the weather station device over the Matter protocol using Zigbee Cluster Library (ZCL).
 The library describes data measurements within the proper clusters that correspond to the measurement type.
 
-The application uses MCUboot secure bootloader and SMP protocol for performing over-the-air Device Firmware Upgrade using Bluetooth LE.
+The application uses MCUboot secure bootloader and SMP protocol for performing over-the-air Device Firmware Upgrade using Bluetooth® LE.
 For information about how to upgrade the device firmware using a PC or a mobile, see the :ref:`matter_weather_station_app_dfu` section.
 
 .. _matter_weather_station_network_mode:

applications/nrf_desktop/README.rst

@@ -7,7 +7,7 @@ nRF Desktop
    :local:
    :depth: 2
 
-The nRF Desktop is a reference design of a Human Interface Device (HID) that is connected to a host through Bluetooth LE or USB, or both.
+The nRF Desktop is a reference design of a Human Interface Device (HID) that is connected to a host through Bluetooth® Low Energy or USB, or both.
 Depending on the configuration, this application can work as desktop mouse, gaming mouse, keyboard, or connection dongle.
 
 .. tip::
@@ -145,11 +145,11 @@ The following threads are kept running in the application:
     * System workqueue thread
     * Logger thread (on debug :ref:`build types <nrf_desktop_requirements_build_types>`)
     * Shell thread (on :ref:`build types <nrf_desktop_requirements_build_types>` with shell enabled)
-    * Threads related to Bluetooth LE (the exact number depends on the selected Link Layer)
+    * Threads related to Bluetooth® LE (the exact number depends on the selected Link Layer)
 * Application-related threads
     * Motion sensor thread (running only on mouse)
     * Settings loading thread (enabled by default only on keyboard)
-    * QoS data sampling thread (running only if Bluetooth LE QoS feature is enabled)
+    * QoS data sampling thread (running only if Bluetooth® LE QoS feature is enabled)
 
 Most of the application activity takes place in the context of the system work queue thread, either through scheduled work objects or through the event manager callbacks (executed from the system workqueue thread).
 Because of this, the application does not need to handle resource protection.
@@ -414,7 +414,7 @@ When it is connected through USB, charging of the rechargeable batteries starts.
 Dongle USB
 ~~~~~~~~~~
 
-The nRF Desktop dongle works as a bridge between the devices connected through standard Bluetooth LE or Low Latency Packet Mode and the host connected through USB.
+The nRF Desktop dongle works as a bridge between the devices connected through standard Bluetooth® Low Energy or Low Latency Packet Mode and the host connected through USB.
 It receives data wirelessly from the connected peripherals and forwards the data to the host.
 
 The nRF Desktop dongle is powered directly through USB.

applications/nrf_desktop/doc/ble_adv.rst

@@ -37,4 +37,4 @@ The nRF Desktop dongle scans for peripheral devices using the Bluetooth device n
 
 
 
-.. |ble_adv| replace:: Bluetooth LE advertising module
+.. |ble_adv| replace:: Bluetooth® LE advertising module

applications/nrf_desktop/doc/ble_bond.rst

@@ -235,4 +235,4 @@ The module uses Zephyr's :ref:`zephyr:settings_api` subsystem to store the follo
 * Currently selected peer (application local identity)
 * Mapping between the application local identities and the Bluetooth local identities
 
-.. |ble_bond| replace:: Bluetooth LE bond module
+.. |ble_bond| replace:: Bluetooth® LE bond module

applications/nrf_desktop/doc/ble_conn_params.rst

@@ -43,8 +43,8 @@ LLPM connections
 
 The Low Latency Packet Mode (LLPM) connection parameters are not supported by the standard Bluetooth.
 
-The LLPM connection parameters update requires using Vendor Sprecific HCI commands.
-Moreover, the peripheral cannot request the LLPM connection parameters using Zephyr Bluetooth API.
+The LLPM connection parameters update requires using vendor-specific HCI commands.
+Moreover, the peripheral cannot request the LLPM connection parameters using Zephyr Bluetooth® API.
 
 Connection interval update
 ==========================
@@ -59,4 +59,4 @@ After the :ref:`nrf_desktop_ble_discovery` completes the peripheral discovery, t
   * **10 ms** otherwise.
     This is required to avoid Bluetooth Link Layer scheduling conflicts that could lead to HID report rate drop.
 
-.. |ble_conn_params| replace:: Bluetooth LE connection parameters module
+.. |ble_conn_params| replace:: Bluetooth® LE connection parameters module

applications/nrf_desktop/doc/ble_discovery.rst

@@ -88,4 +88,4 @@ The same actions are taken if the peripheral's VID and PID value combination is
 The nRF Desktop central works only with predefined subset of peripherals.
 The mentioned peripherals must be described in the :file:`ble_discovery_def.h` file.
 
-.. |ble_discovery| replace:: Bluetooth LE discovery module
+.. |ble_discovery| replace:: Bluetooth® LE discovery module

applications/nrf_desktop/doc/ble_latency.rst

@@ -71,4 +71,4 @@ The module does not register itself using the ``GEN_CONFIG_EVENT_HANDLERS`` macr
 
    For more detailed information, see the :ref:`nrf_desktop_ble_conn_params` documentation page.
 
-.. |ble_latency| replace:: Bluetooth LE latency module
+.. |ble_latency| replace:: Bluetooth® LE latency module

applications/nrf_desktop/doc/ble_qos.rst

@@ -7,7 +7,7 @@ Bluetooth LE Quality of Service module
    :local:
    :depth: 2
 
-Use the Bluetooth LE Quality of Service (QoS) module to achieve better connection quality and higher report rate by avoiding congested RF channels.
+Use the Bluetooth® LE Quality of Service (QoS) module to achieve better connection quality and higher report rate by avoiding congested RF channels.
 The module can be used by both nRF Desktop peripheral and nRF Desktop central with the SoftDevice Link Layer (:kconfig:`CONFIG_BT_LL_SOFTDEVICE`).
 However, only the Bluetooth central can update the Bluetooth LE channel map that is in use.