doc: Minor doc fixes

Minor doc fixes to the NCS docs.

Signed-off-by: divya pillai <[email protected]>

Author: divipillai

applications/nrf_desktop/doc/ble_bond.rst

@@ -171,7 +171,7 @@ The module can go into one of the following standby states to make sure that the
 
 Going into the standby states and leaving these states happens in reaction to the following events:
 
-* ``power_down_event`` - On this event, the module goes into one of the standby states and the ongoing peer operation is cancelled.
+* ``power_down_event`` - On this event, the module goes into one of the standby states and the ongoing peer operation is canceled.
 * ``wake_up_event`` - On this event, the module returns from the standby state.
 
 .. figure:: /images/nrf_desktop_ble_bond_standby.svg

applications/nrf_desktop/doc/usb_state_pm.rst

@@ -31,12 +31,12 @@ It depends on the options :ref:`CONFIG_DESKTOP_USB_ENABLE <config_desktop_app_op
 
 The log level is inherited from the :ref:`nrf_desktop_usb_state`.
 
-System Power Management integration
+System power management integration
 ===================================
 
-Zephyr's System Power Management (:kconfig:option:`CONFIG_PM`) does not automatically take into account (expect) wakeups related to user input and finalized HID report transfers over USB.
+Zephyr's system power management (:kconfig:option:`CONFIG_PM`) does not automatically take into account (expect) wakeups related to user input and finalized HID report transfers over USB.
 This results in entering low power states if no work is scheduled to be done in the nearest future.
-If you use Zephyr's System Power Management, the module automatically requires zero latency in the Power Management while USB is active.
+If you use Zephyr's system power management, the module automatically requires zero latency in the power management while USB is active.
 This is done to prevent entering power states that introduce wakeup latency and ensure high performance.
 You can control this feature using the :ref:`CONFIG_DESKTOP_USB_PM_REQ_NO_PM_LATENCY <config_desktop_app_options>` Kconfig option.
 
@@ -59,9 +59,9 @@ The application power level is imposed using the :c:struct:`power_manager_restri
   The module restricts the power down level to the :c:enum:`POWER_MANAGER_LEVEL_SUSPENDED`.
   The module also submits a :c:struct:`force_power_down_event` to force a quick power down.
 
-System Power Management latency
+System power management latency
 ===============================
 
-The latency requirements of the System Power Management are updated using the :c:func:`pm_policy_latency_request_add` and :c:func:`pm_policy_latency_request_remove` functions.
+The latency requirements of the system power management are updated using the :c:func:`pm_policy_latency_request_add` and :c:func:`pm_policy_latency_request_remove` functions.
 The zero latency requirement is added when USB state is set to :c:enum:`USB_STATE_ACTIVE`.
 The requirement is removed if USB enters another state.

doc/nrf/libraries/modem/at_params.rst

@@ -7,7 +7,7 @@ AT parameters
    :local:
    :depth: 2
 
-.. important::
+.. note::
    The AT parameters module is deprecated.
 
 The AT parameters module provides functionality to store lists of AT command or respond parameters.

samples/bluetooth/peripheral_uart/README.rst

@@ -109,9 +109,6 @@ User interface
 
 The user interface of the sample depends on the hardware platform you are using.
 
-Development kits
-================
-
 .. tabs::
 
    .. group-tab:: nRF21, nRF52 and nRF53 DKs

scripts/docker/README.rst

@@ -16,7 +16,7 @@ The image is based on Linux - Ubuntu 22.04 Docker image with the following addit
   * ``device``
 
 * |NCS| toolchain bundle
-* JLink |jlink_ver| (installation requires accepting SEGGER License)
+* SEGGER J-Link |jlink_ver| (installation requires accepting SEGGER License)
 
 Building image
 **************
@@ -29,16 +29,16 @@ You can use `print_toolchain_checksum.sh`_ to get ID proper for your |NCS| revis
     TOOLCHAIN_ID=$(../print_toolchain_checksum.sh)
     docker build --build-arg VERSION=$TOOLCHAIN_ID
 
-Accepting JLink license
-***********************
+Accepting J-Link license
+************************
 
-To install and use JLink software you have to accept `JLink License Agreement`_.
+To install and use J-Link software you have to accept `JLink License Agreement`_.
 
 If the container is run in an interactive mode, you will be asked to accept the license at the start of the container.
 
-You can also start the container with the ``ACCEPT_JLINK_LICENSE=1`` environment variable, and JLink will be installed without prompting.
+You can also start the container with the ``ACCEPT_JLINK_LICENSE=1`` environment variable, and J-Link will be installed without prompting.
 
-During post installation steps, JLink configures ``udev`` roles.
+During post installation steps, J-Link configures ``udev`` roles.
 This operation requires running a container with the ``--privileged`` flag to grant permissions needed for the container.
 
 Running container
@@ -79,7 +79,7 @@ GitHub Actions
 
 GitHub action starts container with overwritten default entry point. That means you have to set ``bash`` as a default shell to load all required environment variables.
 
-If the container is started with the ``ACCEPT_JLINK_LICENSE`` env variable set to ``1``, JLink will be installed just before the first bash command is executed.
+If the container is started with the ``ACCEPT_JLINK_LICENSE`` env variable set to ``1``, J-Link will be installed just before the first bash command is executed.
 
 Example job configuration: