Edit TS-0022-Field_Device_Configuration.md- 6.1 numbering corrected

TS-0022-Field_Device_Configuration.md

@@ -163,7 +163,7 @@ Figure 6.1-1 depicts three (3) methods, in which ADN or ASN/MN nodes are configu
 
 1. Device Management technologies using the mc reference point defined in clause 6 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. Using this method, the information that is used to configure the ASN/MN or ADN is described as _&lt;mgmtObj>_ resource types that are hosted in the IN-CSE.
 1. oneM2M Mcc and Mca reference point when M2M Service Layer operation has been established to the AE or CSE. Establishment of the M2M Service Layer operation includes actions such as setting up security associations and registration of the M2M entities as per oneM2M TS-0003 <a href="#_ref_3">[3]</a> and oneM2M TS-0001 <a href="#_ref_2">[2]</a>.
-1. To convey the information elements to the ASN/MN nodes that have established M2M Service Layer operation via  Mcc reference points, resource announcement mechanism may be used. In this case, the CSE in the ASN/MN node stores the copy of the &lt;mgmtObj> resource as a _&lt;mgmtObj_Annc>_ resource as shown in the figure 6.1-1.
+   To convey the information elements to the ASN/MN nodes that have established M2M Service Layer operation via  Mcc reference points, resource announcement mechanism may be used. In this case, the CSE in the ASN/MN node stores the copy of the &lt;mgmtObj> resource as a _&lt;mgmtObj_Annc>_ resource as shown in the figure 6.1-1.
 1. oneM2M IPE technology where the IPE interworks the information exchange between the ADN and ASN/MN and the IN-CSE. This type of IPE is called a Configuration IPE in order to depict the role and capabilities of the IPE related to the present document.
 	> NOTE: The reference point between the Configuration IPE and the ADN and ASN/MN is unspecified in the present document.