Update README.md

Author: jtsalten

README.md

@@ -85,7 +85,7 @@ During map generation, by default, the Adaptor sets export and Import conversion
 
 ### How could we configure our mapping for serialization?
 
-We can have as much mapping definitions for a class as we need. An easy way to start to define our customized maps is exporting the default MAP0 and importing it again with a different name, then we can make changes in the map regarding the properties that should be exported /imported, names, conversor methods to apply (See `OPNLib.Serialize.Util` class for tools to export/import maps, get / set property mappings,etc…).
+We can have as much mapping definitions for a class as we need. An easy way to start to define our customized maps is exporting the default MAP0 and importing it again with a different name, then we can make changes in the map regarding the properties that should be exported /imported, names, conversor methods to apply. To do this, we can modify directly in the global, or do it programatically (See `OPNLib.Serialize.Util` class for tools to export/import maps, get / set property mappings,etc…)
 
 ---
 **Example:**
@@ -102,10 +102,10 @@ We can have as much mapping definitions for a class as we need. An easy way to s
  ;Overwrite map (2) of SampleApps.Serialize.MapTesting with map in object:json
  set tSC = ##class(OPNLib.Serialize.Util).ImportMapsFromJSON(json,2,tClassName) 
 
- ;Get settings of one of the properties. They're returned in a json object
+ ;Get settings of one of the properties. They are returned in a json object
  set propExprt = ##class(SampleApps.Serialize.MapTesting).GetMappedPropSettings("code","MAP1",tClassName,1)
 
- ;We'll change the targetPropertyName setting
+ ;We change the targetPropertyName setting
  set $ListUpdate(propExprt.settings,1) = "codeAccepted"
  do ##class(SampleApps.Serialize.MapTesting).SetMappedPropSettings("code",propExprt,"MAP1",tClassName,1)
 
@@ -116,8 +116,6 @@ We can have as much mapping definitions for a class as we need. An easy way to s
 
 ```
 
-
-
 We also have the possibility of changing a bit the way in which default map `MAP0` is generated :
 * Change the name of default map. 
  * Use parameter `EXPTDEFAULTMAP` to indicate a name for default map before compiling the class 
@@ -128,30 +126,26 @@ We also have the possibility of changing a bit the way in which default map `MAP
 * Drill down levels
  * Use `EXPTDRILLDOWN`To indicate up to what number of levels that the export/import logic should follow through object references. 0 means no drill down. A positive number(n) means to drill down n times through the chain of references.
 
+## How did it work the default mechanism?
 
+Both methods, `Export` and `Import` will call the generated methods: `exportStd` and `importStd` respectively. These two methods will go through the global `^MAPS` and `^MAPSREV` respectively, looking for the properties to export /import and applying the required conversions. 
+Both methods work over an already instantiated method. This is particularly interesting for import, as we can have an object in memory with some data already and import the rest of the data from a serialized object. The import mechanism will replace with the new content the properties contained in the serialization but will preserve other properties already set in the instance that are not included in the serialization that we import.
 
-How did it work the default mechanism?
-
-Both methods, export and Import will call the generated methods: exportStd and imoortStd respectively. These two methods will go through the global ^MAPS and ^MAPSREV respectively, looking for the properties to export /import and applying the required conversions. 
-Both methods work over an already instantiated method. This is particularly important for import, as we can have an object in memory with some data already and import the rest of the data from a serialized object. The import mechanism will replace with the new content the properties contained in the serialization but will preserve other properties already set in the instance that are not included in the serialization that we import.
-
-Example:
+This way of working give us the flexibility of using different mappings using the same autogenerated code but it can have a penalty in performance if we use it massively in loops or in very high concurrency use cases. Anyway, better test in such scenarios. 
 
-<< import a JSON with just some properties in an object where we already have some others set >>>
+## Some considerations about performance 
 
-This way of working give us the flexibility of using different mappings using the same autogenerated code but it can have a penalty in performance if we use it massively in loops or in very high concurrency use cases. Anyway,better test in such scenarios. 
+As it was already mentioned, the default mechanism resolve the mapping sets at real time, trasversing a global to set the properties to export/import targets. That means that this mechanism will always be slower than if we already had that settings resolved at compile time. In order to provide that functionality, we can use the Template classes. 
 
-Some considerations about performance 
+## What are the template classes for?
 
-As we already mentioned, the default mechanism resolve the mapping sets at real time, trasversing a global to set the properties to export/import targets. That means that this mechanism will always be slower than if we already had that settings resolved at compile time. In order to provide that functionality, we can use the Template classes. 
-
- What are the template classes for?
-
-The templates classes allow us to generate the logic to export /import at compile time.
+The templates classes allow us to generate the logic to export/import at compile time.
 This have benefits over performance but comes at the price of having to use a different class for each type of serialization format and mapping.
 
 Anyway, the primary class is not affected and doesn't have to be changed no matter how many templates define to handle the serialization of its objects.
 
+
+
 Example :
 
 <<< define and use different template classes, for different maps in JSON and also for different serialization (CSV)