diff --git a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md
index da47d6f084a171fe468c891e5f95e5a3d7bd7a3f..31495743babaa5bc09aacbf22a0d112318941b06 100644
--- a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md	
+++ b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md	
@@ -6,7 +6,7 @@ System Information (SI) is divided into the *MIB* and a number of SIBs and posSI
 
 - the *MIB* is always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms (TS 38.212 \[17\], clause 7.1) and it includes parameters that are needed to acquire *SIB1* from the cell. The first transmission of the *MIB* is scheduled in subframes as defined in TS 38.213 \[13\], clause 4.1 and repetitions are scheduled according to the period of SSB;
 
-**NOTE** 1: If the period of SSB is larger than 80 ms, the MIB is transmitted with the same periodicity as that of SSB.
+**NOTE 1**: If the period of SSB is larger than 80 ms, the MIB is transmitted with the same periodicity as that of SSB.
 
 - the *SIB1* is transmitted on the DL-SCH with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms as specified in TS 38.213 \[13\], clause 13. The default transmission repetition periodicity of *SIB1* is 20 ms but the actual transmission repetition periodicity is up to network implementation. For SSB and CORESET multiplexing pattern 1, *SIB1* repetition transmission period is 20 ms. For SSB and CORESET multiplexing pattern 2/3, *SIB1* transmission repetition period is the same as the SSB period (TS 38.213 \[13\], clause 13). *SIB1* includes information regarding the availability and scheduling (e.g. mapping of SIBs to SI message, periodicity, SI-window size) of other SIBs with an indication whether one or more SIBs are only provided on-demand and, in that case, the configuration needed by the UE to perform the SI request. *SIB1* is cell-specific SIB;
 
@@ -18,7 +18,7 @@ System Information (SI) is divided into the *MIB* and a number of SIBs and posSI
 
 - For PSCell and SCells, the network provides the required SI by dedicated signalling, i.e. within an *RRCReconfiguration* message. Nevertheless, the UE shall acquire *MIB* of the PSCell to get SFN timing of the SCG (which may be different from MCG). Upon change of relevant SI for SCell, the network releases and adds the concerned SCell. For PSCell, the required SI can only be changed with Reconfiguration with Sync.
 
-**NOTE** 2: The physical layer imposes a limit to the maximum size a SIB can take. The maximum *SIB1* or *SI message* size is 2976 bits.
+**NOTE 2**: The physical layer imposes a limit to the maximum size a SIB can take. The maximum *SIB1* or *SI message* size is 2976 bits.
 
 ### 5.2.2 System information acquisition
 
@@ -47,7 +47,7 @@ When the UE acquires a *MIB* or a *SIB1* or an SI message in a serving cell as d
 
 A L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform the interested SIB(s) to the connected L2 U2N Relay UE as defined in clause 5.8.9.8.2 and receive the SIB(s) from the L2 U2N Relay UE as defined in clause 5.8.9.9.3. A L2 U2N Remote UE in RRC_CONNECTED receives SIB1 and other SIB(s) in *RRCReconfiguration* message and performs on-demand SI request if required, as defined in clause 5.2.2.3.5 and 5.2.2.3.6. The L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED (when MP is not configured) is not required to obtain SI over Uu interface, but it may decide to perform the SI acquisition procedure over Uu interface as defined in clause 5.2.2.3 by UE implementation.
 
-*NOTE*: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation.
+**NOTE**: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation.
 
 The UE shall: