Apply suggestions from code review

Co-authored-by: Francesco Domenico Servidio <[email protected]>

doc/nrf/app_dev/device_guides/working_with_nrf/nrf54h/ug_nrf54h20_suit_sdfw_sdrfw_update.rst

@@ -7,17 +7,13 @@ Secure Domain Firmware Update
    :local:
    :depth: 2
 
-Background
-**********
 
 Both the Secure Domain Firmware (SDFW) and the recovery image for the Secure Domain Firmware are launched on a core responsible for establishing the Root of Trust as a Secure Domain.
-Due to security requirements, the update process for these binaries differs significantly from regular updates in Local Domains.
+Due to security requirements, the update process for these binaries differs significantly from regular updates in local domains.
 
 To ensure that trusted execution can be established on the device, a valid recovery image for the Secure Domain Firmware must be present on the device before performing a Secure Domain Firmware update.
 An update is initiated only if the update candidate is verified by the Secure Domain ROM using a key that matches the requested update type.
 
-
-
 The SUIT framework allows flexible firmware launching and updating while keeping parts of the codebase unmodifiable by end users.
 A common approach is to use a platform-specific layer that maps firmware blocks to device memory ranges, simplifying updates for basic systems.
 Manifests can describe actions required to launch or update each firmware block.
@@ -30,7 +26,6 @@ Implementation
 SUIT manifests use components to define executable or updatable entities.
 On a given platform, components may have different characteristics that require varied approaches for launching or updating (for example, execution in place instead of copying to RAM).
 
-
 As described in :ref:`suit_component_types`, a special SUIT component type (``SOC_SPEC``) describes components that are controlled by Nordic Semiconductor.
 
 For the nRF54H20 SoC, there are two components of this type: one for the SDFW and the other for the SDFW recovery image.