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..27130557b2ad721772fd4d87f0a35bba3620d983 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	
@@ -8,7 +8,7 @@ System Information (SI) is divided into the *MIB* and a number of SIBs and posSI
 
 **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;
+- the *SIB1* is transmitted on the DL-SCH with a periodicity of 160 ms or more or less 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;
 
 - SIBs other than *SIB1* and posSIBs are carried in *SystemInformation* (SI) messages, which are transmitted on the DL-SCH. Only SIBs or posSIBs having the same periodicity can be mapped to the same SI message. SIBs and posSIBs are mapped to different SI messages, i.e. an SI message contains either only SIBs or only posSIBs. Each SI message is transmitted within periodically occurring time domain windows (referred to as SI-windows with same length for all SI messages). Each SI message is associated with an SI-window and the SI-windows of different SI messages do not overlap. That is, within one SI-window only the corresponding SI message is transmitted. An SI message may be repeated with the same content a number of times within the SI-window. Any SIB or posSIB except *SIB1* can be configured to be cell specific or area specific, using an indication in *SIB1*. The cell specific SIB is applicable only within a cell that provides the SIB while the area specific SIB is applicable within an area referred to as SI area, which consists of one or several cells and is identified by s*ystemInformationAreaID*;
 
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 6aa1fa29299a4be59ce7ca3e4da0230136bed82c..40f4788efa46a5ccb65b40f745adfd8131be9a68 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	
@@ -16,7 +16,7 @@
 
 [Figure 5.3.3.1-2: RRC connection setup, network reject][Figure 5.3.3.1-2]
 
-The purpose of this procedure is to establish an RRC connection between the UE and the RAN.
+The purpose of this procedure is to establish an RRC connection between the UE and the RAN system.
 
 #### 6.1.1.2 Initiation
 
diff --git a/specification/stage-3/06_Connection_Control/figures/xx.01.01-01 Connection Setup - success.msc b/specification/stage-3/06_Connection_Control/figures/xx.01.01-01 Connection Setup - success.msc
index 30068d8ad56e0af266c400bfa90f7f23461f6720..c1e03c2901702b812ca96a4aeadb90e82f343091 100644
--- a/specification/stage-3/06_Connection_Control/figures/xx.01.01-01 Connection Setup - success.msc	
+++ b/specification/stage-3/06_Connection_Control/figures/xx.01.01-01 Connection Setup - success.msc	
@@ -10,7 +10,7 @@ u: UE;
 n: Network;
 
 |||;
-u->n: ConnectionSetupRequest [ac];
+u->n: ConnectionSetupRequest1 [ac];
 u<-n: ConnectionSetup [ac];
-u->n: ConnectionSetupComplete [ac];
+u->n: ConnectionSetupComplete1 [ac];
 |||;