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 b87d14e872086d0604824d042cb0f6c7369ab99d..24c5ccd49d1cb6e4a7dd56dcbe8d739c85bf281d 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	
@@ -4,7 +4,7 @@
 
 System Information (SI) is divided into the *MIB* and a number of SIBs and posSIBs where:
 
-- 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;
+- 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 re-scheduled according to the period of SSB;
 
 **NOTE** 1: If the period of SSB is larger than 20 ms, the MIB is transmitted with the same periodicity as that of SSB.
 
diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md
index 3312160aa4a6f74cebf03da87b49159bb75d3f4c..8bb3097a46b5bc479c7010d4896cfa7dbbdd7855 100644
--- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md	
+++ b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md	
@@ -20,11 +20,11 @@ The purpose of this procedure is to establish an RRC connection between the UE a
 
 #### 6.1.1.2 Initiation
 
-The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information (or when it performs successful failure).
+The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information (or when it performs the procedures for another feature or when it performs successful failure).
 
 The UE shall ensure having valid and up to date essential SI as specified in clause 5.2.2.2 before initiating this procedure.
 
-Upon initiation of the procedure, the UE shall:
+Upon initiation of the procedure, the UE shall also:
 
 - perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers;