reviewed consumption model. improved overall score from 84 to 94, style from 67 to 100, clarity from 73 to 90, and tone from 64 to 79

Author: farah-alyasari

articles/azure-maps/consumption-model.md

@@ -1,6 +1,6 @@
 ---
 title: Vehicle consumption models for routing | Microsoft Azure Maps
-description: In this article, you will learn about vehicle consumption models for routing in Microsoft Azure Maps. 
+description: In this article, you'll learn about vehicle consumption models for routing in Microsoft Azure Maps. 
 author: subbarayudukamma
 ms.author: skamma
 ms.date: 05/08/2018
@@ -13,21 +13,20 @@ manager:
 
 # Consumption model
 
-Online Routing provides a set of parameters for a detailed description of vehicle-specific Consumption Model.
-Depending on the value of **vehicleEngineType**, two principal Consumption Models are supported: _Combustion_ and _Electric_. Specifying parameters that belong to different models in the same request is an error.
-Consumption Model cannot be used with **travelMode** values _bicycle_ and _pedestrian_.
+The Routing service provides a set of parameters for a detailed description of the vehicle-specific Consumption Model.
+Depending on the value of **vehicleEngineType**, two principal Consumption Models are supported: _Combustion_ and _Electric_. It's incorrect to specify parameters that belong to different models in the same request. Also, Consumption Model parameters can't be used with the following **travelMode** values: _bicycle_ and _pedestrian_.
 
 ## Parameter constraints for consumption model
 
-In both Consumption Models, explicitly specifying some parameters requires specifying some others as well. These dependencies are:
+In both Consumption Models, there are some dependencies when specifying parameters. Meaning that, explicitly specifying some parameters may require specifying some other parameters. Here are these dependencies to be aware of:
 
-* All parameters require **constantSpeedConsumption** to be specified by the user. It is an error to specify any other consumption model parameter, with the exception of **vehicleWeight**, if **constantSpeedConsumption** is not specified.
-* **accelerationEfficiency** and **decelerationEfficiency** must always be specified as a pair (i.e. both or none).
+* All parameters require **constantSpeedConsumption** to be specified by the user. It is an error to specify any other consumption model parameter, if **constantSpeedConsumption** is not specified. The **vehicleWeight** parameter is an exception for this requirement.
+* **accelerationEfficiency** and **decelerationEfficiency** must always be specified as a pair (that is, both or none).
 * If **accelerationEfficiency** and **decelerationEfficiency** are specified, product of their values must not be greater than 1 (to prevent perpetual motion).
-* **uphillEfficiency** and **downhillEfficiency** must always be specified as a pair (i.e. both or none).
+* **uphillEfficiency** and **downhillEfficiency** must always be specified as a pair (that's, both or none).
 * If **uphillEfficiency** and **downhillEfficiency** are specified, product of their values must not be greater than 1 (to prevent perpetual motion).
 * If the \*__Efficiency__ parameters are specified by the user, then **vehicleWeight** must also be specified. When **vehicleEngineType** is _combustion_, **fuelEnergyDensityInMJoulesPerLiter** must be specified as well.
-* **maxChargeInkWh** and **currentChargeInkWh** must always be specified as a pair (i.e. both or none).
+* **maxChargeInkWh** and **currentChargeInkWh** must always be specified as a pair (that is, both or none).
 
 > [!NOTE]
 > If only **constantSpeedConsumption** is specified, no other consumption aspects like slopes and vehicle acceleration are taken into account for consumption computations.
@@ -64,5 +63,5 @@ The list of parameters that belong to this model are below. Refer to the Paramet
 
 ## Sensible values of consumption parameters
 
-A particular set of consumption parameters can be rejected, even though it might fulfill all the explicit requirements specified above. It happens when the value of a specific parameter, or a combination of values of several parameters, is deemed to lead to unreasonable magnitudes of consumption values. If that happens, it most likely indicates an input error, as proper care is taken to accommodate all sensible values of consumption parameters. In case a particular set of consumption parameters is rejected, the accompanying error message will contain a textual explanation of the reason(s).
+A particular set of consumption parameters can be rejected, even though the set might fulfill all the explicit requirements. It happens when the value of a specific parameter, or a combination of values of several parameters, is considered to lead to unreasonable magnitudes of consumption values. If that happens, it most likely indicates an input error, as proper care is taken to accommodate all sensible values of consumption parameters. In case a particular set of consumption parameters is rejected, the accompanying error message will contain a textual explanation of the reason(s).
 The detailed descriptions of the parameters have examples of sensible values for both models.