EN/CityGML-Tutorial/chapter-1:-Intro-CityGML.md

@@ -27,7 +27,7 @@ The following UML diagram defines the CityGML top level class hierarchy (based o
 
 A _City Model_ is a collection of _cityObjectMembers_. Each CityGML Module defines specific _CityObjects_ such as _Building_ objects, _Vegetation_ objects etc. Every _CityObject_ has a fixed set of specific attributes as specified in the UML model, and an _Appearance_ do define its visual properties. _GenericAttributes_ can be used to define additional attributes that are not explicitly specified in the UML model itself.
 
-The XML encoding of the UML diagram is defined in an XML schema. In CityGML 2.0, the XML schema part of the CityGML standard document. An example of a typical XML document - the CityModel - is sketched here:
+The XML encoding of the UML diagram is defined in an XML schema. In CityGML 2.0, the XML schema is a part of the CityGML standard document. An example of a typical XML document of a _City Model_ is sketched here:
 
 ```plaintext
 <?xml version="1.0" encoding="UTF-8"?>  
@@ -47,8 +47,7 @@ The XML encoding of the UML diagram is defined in an XML schema. In CityGML 2.0,
 </core:CityModel>   
 ```
 
-In CityGML 3.0, the UML model is defined in the conceptual model standard. Multiple encodings can exist to encode the conceptual model. One encoding is the XML encoding. With CityJSON, another encoding of the conceptual model is available.
-
+In CityGML 3.0, only the UML model is defined in the conceptual model standard document. Unlike CityGML 2.0 multiple encodings can exist for CityGML 3.0 to encode the conceptual model. One encoding is the [XML](https://github.com/opengeospatial/CityGML-3.0Encodings/tree/master/Moved_to_CITYGML-3.0Encoding_CityGML) encoding. Other encodings such as CityDotNet, CityJSON, CitySQL are under [development](https://github.com/opengeospatial/CityGML-3.0Encodings).
 ## References:
 
 [OGC CityGML standard](https://www.ogc.org/standards/citygml)