#2 style

docs/web/docs/Simulation/VehiclePermissions.md

@@ -80,9 +80,9 @@ should be used.
 The default vehicle classes (including the values `custom1` and `custom2`) can handle most requirements for modelling network access restrictions.
 However, in some domains such as shipping (draught, beam) and railroads (axle weight, grade), it may be necessary to provide for fine grained numerical access models.
 
-For this, [duarouter](../duarouter.md) provides the option **--restriction-params** to handle set list of edge and vehicle type [generic parameters](GenericParameters.md) names.
+For this, [duarouter](../duarouter.md) provides the option **--restriction-params** to set list of edge and vehicle type [generic parameters](GenericParameters.md) names.
 
-- Only those vehicles where the restriction param has a lowever value than the corresponding edge param are allowed to move on an edge.
+- Only those vehicles where the restriction param has a lower value than the corresponding edge param are allowed to move on an edge.
 - If a `<vType>` does not define a restriction param it's value is initialized to *0*.
 - If an `<edge>` does not define a restriction param it's value is initialized to *1e40*.
 
@@ -92,7 +92,7 @@ Restrictions on ship draught could be modelled in the following manner:
 
 where *net.net.xml* has an edge defined as
 
-```
+```xml
 <edge id="E" from="beg" to="end" priority="-1">
         <lane id="E_0" index="0" allow="ship" speed="13.90" length="100"/>
         <param key="draught" value="10"/>
@@ -101,7 +101,7 @@ where *net.net.xml* has an edge defined as
 
 and *routes.rou.xml* defined with the following types:
 
-```
+```xml
     <vType id="0" vClass="ship">
         <param key="draught" value="5"/>
     </vType>