Apply suggestions from code review

Co-authored-by: Divya S Pillai <91891495+divipillai@users.noreply.github.com>

Author: MarkusLassila

doc/app/at_trace.rst

@@ -20,7 +20,7 @@ See :ref:`sm_logging_uart_backend` for a full description of the feature.
 The Zephyr application log backend (``AT#XLOG``) and the modem trace backend (``AT#XTRACE``) share a single UART.
 They are mutually exclusive: enabling one while the other is active returns an error.
 During boot, the UART outputs logs from B0, MCUboot, and the application.
-After application initialization, the UART is suspended when neither backend is active and resumed when either backend is enabled.
+After initialization, the UART is suspended when no backend is active and resumed when at least one backend is enabled.
 
 The trace UART is configured at 1000000 baud rate to support the high data rate required for the modem traces.
 Trace data is available through the UART1 interface (VCOM1 on the nRF9151 DK).

doc/app/sm_logging.rst

@@ -14,7 +14,7 @@ Application logging
 *******************
 
 |SM| outputs B0, MCUboot, and application logs over ``UART1`` (VCOM1 on the nRF9151 DK) during boot.
-After the application is initialized, the log backend is disabled and the UART is suspended.
+After the application is initialized, the log backend is disabled, and the UART is suspended.
 Use ``AT#XLOG=1`` to enable application logs and resume the UART.
 This avoids UART power overhead when logs are not needed during normal operation.
 See :ref:`SM_AT_trace` for the full command reference.