Final cleanup (sic)

Signed-off-by: Ulf Bjorkengren <[email protected]>

tools/DomainConversionTool/README.md

@@ -22,7 +22,7 @@ Mapping:<br>
 - North: signal-name<br>
   South: signal-name<br>
 An example of a mapping file is shown below.<br>
-![Signal mapping example](/pics/Signal-mapping.png?pct=75)
+![Signal mapping example](/pics/Signal-mapping.png?pct=75)<br>
 The DCT directory contains three signal description files:<br>
 * CAN-v0.1.yaml // A southbound domain example describing 5 CAN signals
 * VSS-v0.1.yaml // A northbound domain example describing 6 VSS signals
@@ -31,6 +31,10 @@ The DCT directory contains three signal description files:<br>
 The directory also contain a mapping file example for mapping signals from the CAN-v0.1 domain with signals from the VSS-v0.1 domain.
 * MAP-VSSv0.1-CANv0.1.yaml
 
+For scaling due to different units representing the data of the two domains the DCT reads a file containing linear scaling coefficients.
+This file can be augmented with more unit scalings than its current examples.
+* UnitScaling.yaml
+
 DCT provides the following operations, that are selected by adding a command parameter to the DCT start command.
 * domains // displays the domains that have been imported by the tool, i. e. that are stored in tables of the tool database.
 * datamodel // displays the domains that have been imported by the tool, i. e. that are stored in tables of the tool database.
@@ -78,7 +82,7 @@ The other two files that were generated by the DCT are stored in the directory o
 or else the files can be renamd to the names tht the feeder tries to read per default, "VssVehicle.cvt" and VssVehicleScaling.json".
 
 ## DCT limitations
-This first verion of the DCT has some known limitations that are expected to be mitigated in later versions.
+This first version of the DCT has some known limitations that are expected to be mitigated in later versions.
 * Arrays in the YAML input files cannot use the syntax [elem1, .., elemN] but must be represented as
 ```
  - elem1