Apply suggestions from code review

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

Author: MarkusLassila

doc/app/sm_releasing.rst

@@ -3,11 +3,11 @@
 Releasing |SM|
 ##############
 
-Before each official release or pre-release, update the version metadata below.
+Before each official release or pre-release, update the following version metadata.
 Each published application image must carry a higher MCUboot sign version than the previous one on the same product line.
 Increment ``CONFIG_FW_INFO_FIRMWARE_VERSION`` only when the MCUboot bootloader image changes.
 
-Application — :file:`app/VERSION`
+Application - :file:`app/VERSION`
 =================================
 
 :file:`app/VERSION` is the single source of truth for:
@@ -21,14 +21,15 @@ DFU and ``AT#XSMVER``
 ---------------------
 
 For application firmware update, a host can read ``AT#XSMVER`` before and after DFU and compare the ``major.minor.patchlevel`` prefix of ``<sm_version>`` (the part from :file:`app/VERSION`, before any ``-N-g<hash>`` Git suffix).
-That value must increase when moving to a newer published image; MCUboot enforces the same ordering via the sign version derived from :file:`app/VERSION`.
+That value must increase when moving to a newer published image.
+MCUboot enforces the same ordering using the sign version derived from :file:`app/VERSION`.
 The Git suffix is informational only and is not used for downgrade checks.
 
 Pre-release numbering
 ---------------------
 
 Before General Availability (GA) for a target ``X.Y.Z``, use a staging line below ``X.Y.Z`` and increment ``PATCHLEVEL`` for each published pre-release.
-Keep ``VERSION_TWEAK = 0`` unless you have a separate reason to use it after GA.
+Keep ``VERSION_TWEAK = 0`` unless you have a specific reason to use it after GA.
 
 v2.0.0 GA
 ~~~~~~~~~
@@ -65,7 +66,7 @@ At GA, set the product version to ``2.0.0``.
 Future v2.1.0 GA
 ~~~~~~~~~~~~~~~~
 
-Pre-releases before v2.1.0 GA use the ``2.0.99`` line (for example ``2.0.99``, then ``2.0.100``), incrementing ``PATCHLEVEL`` for each published pre-release—the same pattern as ``1.99.0``, ``1.99.1`` before v2.0.0 GA.
+Pre-releases before v2.1.0 GA, use the ``2.0.99`` line (for example ``2.0.99``, then ``2.0.100``), incrementing ``PATCHLEVEL`` for each published pre-release, following the same pattern as ``1.99.0``, ``1.99.1`` before v2.0.0 GA.
 At v2.1.0 GA, set ``VERSION_MAJOR``, ``VERSION_MINOR``, and ``PATCHLEVEL`` to ``2``, ``1``, and ``0``.
 
 General Availability and later
@@ -81,11 +82,9 @@ Confirm the version with :ref:`SM_AT_XSMVER`.
 MCUboot — ``CONFIG_FW_INFO_FIRMWARE_VERSION``
 =============================================
 
-:file:`app/sysbuild/mcuboot/prj.conf`
-
-Increment only when the MCUboot bootloader image changes.
-Used by NSIB (B0) for MCUboot slot downgrade prevention — independent of :file:`app/VERSION`.
+In :file:`app/sysbuild/mcuboot/prj.conf`, increment the value only when the MCUboot bootloader image changes.
+The value is used by NSIB (B0) for MCUboot slot downgrade prevention and is independent of :file:`app/VERSION`.
 
 After an MCUboot update, ``AT#XBOOTINFO=0`` reports the active slot value.
 
-See :ref:`serial_modem_release_notes`.
+See :ref:`serial_modem_release_notes` for more information.

doc/releases/migration_notes_v2.0.0.rst

@@ -28,14 +28,14 @@ Informational changes
 
 The following changes are listed for informational purposes, and many hosts will work without any changes.
 
-* Application rollback prevention — Application firmware DFU now uses MCUboot downgrade prevention (``CONFIG_MCUBOOT_DOWNGRADE_PREVENTION``).
+* Application rollback prevention - Application firmware DFU now uses MCUboot downgrade prevention (``CONFIG_MCUBOOT_DOWNGRADE_PREVENTION``).
   The device rejects signed application images older than the version currently running.
   Set :file:`app/VERSION` before each published build; see :ref:`sm_releasing`.
 
-* ``AT#XSMVER`` — No change to the response layout for hosts.
+* ``AT#XSMVER`` - No change to the response layout for hosts.
   ``<sm_version>`` is still a quoted Git-describe-style string (for example ``"v2.0.0-18-g2c85d9224fca"``).
   Existing parsers can keep using it as in v1.x.x.
-  The ``major.minor.patch`` part now follows :file:`app/VERSION` (same value used for rollback prevention); the ``-N-g<hash>`` suffix still comes from Git.
+  The ``major.minor.patch`` part now follows :file:`app/VERSION` (same value used for rollback prevention), the ``-N-g<hash>`` suffix still comes from Git.
 
 * Ring Indication (RI) - Change RI from pulse (100 ms) to level triggered, meaning RI stays asserted until the host asserts DTR.
   After the Serial Modem has enabled UART, RI will be deasserted.