doc: general doc update using VALE

Updated docs to fix VALE-triggered errors.

Signed-off-by: Francesco Domenico Servidio <[email protected]>

Author: FrancescoSer

applications/hpf/mspi/README.rst

@@ -255,7 +255,7 @@ Key functions, such as :c:func:`hrt_write`, :c:func:`hrt_tx`, and :c:func:`hrt_r
        3. Transfers the frame elements sequentially via :c:func:`hrt_tx`.
        4. Manages clock timing and CE pin behavior.
    * - :c:func:`hrt_tx`
-     - Handles the low-level data transfer for a specific frame element (e.g., ``command``, ``address``, ``dummy_cycles``, or ``data``).
+     - Handles the low-level data transfer for a specific frame element (for example, ``command``, ``address``, ``dummy_cycles``, or ``data``).
      - 1. Configures the shift controller (:c:func:`nrf_vpr_csr_vio_shift_ctrl_buffered_set`).
        2. Writes each word from the data buffer to the output register.
        3. Starts the hardware counter for generating clock signal.

applications/machine_learning/app_desc.rst

@@ -660,7 +660,7 @@ Forwarding data.
 
    a. Open the `nRF Connect for Mobile`_ application and connect to the device again.
    #. Bond with the device from the `nRF Connect for Mobile`_ application on your smartphone or tablet.
-   #. Find **Nordic UART Service** and enable notification of its "TX Characteristic".
+   #. Find :guilabel:`Nordic UART Service` and enable notification of its :guilabel:`TX Characteristic`.
    #. Observe the sensor readouts represented as comma-separated values.
       Every new value represents a single sensor readout.
 

applications/matter_bridge/doc/matter_bridge_description.rst

@@ -434,12 +434,14 @@ CONFIG_BRIDGE_TEMPERATURE_SENSOR_BRIDGED_DEVICE
 .. _CONFIG_BRIDGE_MIGRATE_PRE_2_7_0:
 
 CONFIG_BRIDGE_MIGRATE_PRE_2_7_0
-``bool`` - Enable migration of bridged device data stored in old scheme from pre |NCS| 2.7.0 releases.
+   ``bool`` - Enable migration of bridged device data stored in old scheme from pre |NCS| 2.7.0 releases.
 
 .. _CONFIG_BRIDGE_MIGRATE_VERSION_1:
 
 CONFIG_BRIDGE_MIGRATE_VERSION_1
-``bool`` - Enable migration of bridged device data stored in version 1 of new scheme.If you selected the simulated device implementation using the :ref:`CONFIG_BRIDGED_DEVICE_SIMULATED <CONFIG_BRIDGED_DEVICE_SIMULATED>` Kconfig option, also check and configure the following option:
+   ``bool`` - Enable migration of bridged device data stored in version 1 of new scheme.
+
+   If you selected the simulated device implementation using the :ref:`CONFIG_BRIDGED_DEVICE_SIMULATED <CONFIG_BRIDGED_DEVICE_SIMULATED>` Kconfig option, also check and configure the following option:
 
 .. _CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_IMPLEMENTATION:
 

applications/nrf_desktop/description.rst

@@ -696,7 +696,7 @@ The assignments of hardware interface elements depend on the device type.
 
           1. Short-press to toggle between available peers.
              **LED1** blinks rapidly for each peer.
-             The amount of blinks corresponds to the number assigned to a peer: one blink for peer 1, two blinks for peer 2, and so on.
+             The amount of blinks corresponds to the number assigned to a peer (for example, one blink for peer 1, two blinks for peer 2), increasing incrementally with each peer.
           #. Double-press to confirm the peer selection.
              The peer is changed after the confirmation.
              **LED1** becomes solid for a short time and then turns itself off.

applications/nrf_desktop/doc/config_channel.rst

@@ -364,7 +364,7 @@ For reading the module descriptor, the following conditions must be met:
 * The module name should be provided as the first string in the module descriptor.
 * The following strings should indicate the module option names.
   The first option on the descriptor must be identified with Option ID equal to ``1``.
-  The following options will be identified by monotonically increasing Option ID values (second option by ``2``, third by ``3``, and so on).
+  The following options will be identified by monotonically increasing Option ID values, starting from ``2`` for the second option, ``3`` for the third, and continuing incrementally.
 * Once the descriptor is read, the module options can be accessed.
   When performing a set or fetch request on the option, the Event ID contains the Option ID and the Module ID of the module that owns the option.
 
@@ -406,8 +406,8 @@ Depending on the connection method:
    To prevent HID input report rate drop while forwarding config channel report set operation, nRF Desktop Dongle can forward the data using GATT write without response.
    In that case, the peripheral does not have to provide the GATT write response instead of sending the HID input report.
 
-   The "GATT write without response" operation cannot be performed on the HID feature report.
-   To allow the "GATT write without response", the Peripheral must provide an additional HID output report.
+   The *GATT write without response* operation cannot be performed on the HID feature report.
+   To allow the GATT write without response, the Peripheral must provide an additional HID output report.
    Use the :ref:`CONFIG_DESKTOP_CONFIG_CHANNEL_OUT_REPORT <config_desktop_app_options>` Kconfig option in the nRF Desktop peripheral configuration to add the mentioned HID output report.
    Disabling this option reduces the memory consumption.
 

applications/serial_lte_modem/doc/SMS_AT_commands.rst

@@ -49,7 +49,7 @@ This is the notification syntax when an SMS message is received:
 
   * The ``<datetime>`` value is a string.
     It represents the time when the SMS is received.
-    It has a format of "YY-MM-DD HH:MM:SS".
+    It has a format of ``YY-MM-DD HH:MM:SS``.
   * The ``<number>`` value is a string.
     It represents the SMS sender's phone number.
   * The ``<text>`` value is a string.

applications/serial_lte_modem/doc/SOCKET_AT_commands.rst

@@ -439,7 +439,7 @@ Response syntax
 
 * The ``<sec_tag>`` value is an integer.
   It indicates to the modem the credential of the security tag to be used for establishing a secure connection.
-  For a non-secure socket, it returns the value of -1.
+  For a non-secure socket, it returns the value of –1.
 
 * The ``<ranking>`` value is an integer.
   It indicates the ranking value of this socket, where the largest value means the highest ranking.

applications/serial_lte_modem/doc/slm_description.rst

@@ -333,7 +333,7 @@ The following configuration files are provided:
 
 * :file:`overlay-ppp-without-cmux.overlay` - Devicetree overlay that configures the UART to be used by PPP.
   This configuration file should be included when building SLM with PPP and without CMUX, in addition to :file:`overlay-ppp.conf`.
-  It can be customized to fit your configuration (UART, baud rate, and so on).
+  It can be customized to fit your configuration, such as UART settings, baud rate, and flow control.
   By default, it sets the baud rate of the PPP UART to 1 000 000.
 
 * :file:`overlay-memfault.conf` - Configuration file that enables `Memfault`_.

applications/serial_lte_modem/doc/slm_testing.rst

@@ -1323,7 +1323,7 @@ Complete the following steps to test the functionality provided by the :ref:`SLM
          226 Transfer complete.
          OK
 
-   #. Navigate to the :file:`upload` folder, switch to binary transfer mode, and create a binary file with the content "DEADBEEF".
+   #. Navigate to the :file:`upload` folder, switch to binary transfer mode, and create a binary file with the content ``DEADBEEF``.
 
       .. parsed-literal::
          :class: highlight
@@ -1342,7 +1342,7 @@ Complete the following steps to test the functionality provided by the :ref:`SLM
          226 Transfer complete.
          OK
 
-   #. Switch to ASCII transfer mode and create a text file with the content "TEXTDATA".
+   #. Switch to ASCII transfer mode and create a text file with the content ``TEXTDATA``.
 
       .. parsed-literal::
          :class: highlight
@@ -1366,7 +1366,7 @@ Complete the following steps to test the functionality provided by the :ref:`SLM
          221 Goodbye.
          OK
 
-#. Test an FTP connection to "ftp.dlptest.com".
+#. Test an FTP connection to ``ftp.dlptest.com``.
 
    This server does not support anonymous login.
    Go to `DLPTest.com`_ to get the latest login information.
@@ -1441,7 +1441,7 @@ Complete the following steps to test the functionality provided by the :ref:`SLM
          250 OK. Current directory is /newfolder
          OK
 
-   #. Switch to binary transfer mode and create a binary file with the content "DEADBEEF".
+   #. Switch to binary transfer mode and create a binary file with the content ``DEADBEEF``.
 
       .. parsed-literal::
          :class: highlight

doc/nrf/app_dev.rst

@@ -7,7 +7,7 @@ Application development
 The user guides in this section cover topics related to the general processes governing the application development in the |NCS|, from :ref:`creating an application <create_application>` to its customization for a specific device.
 Read these guides together with Zephyr's :ref:`zephyr:application` documentation.
 
-For detailed integration instructions of specific technologies and components, check the pages in other top sections of the documentation (Protocols, Applications, Samples, and so on).
+For detailed integration instructions of specific technologies and components, check the pages in other top sections of the documentation (like Protocols, Applications, or Samples).
 
 .. figure:: /images/ncs_app_dev.svg
    :alt: Application development section overview