updating PR review feedback

Author: uhabiba04

articles/industry/agriculture/ingest-historical-telemetry-data.md

@@ -96,8 +96,8 @@ Follow the below steps to generate these:
 |          SensorMeasures > DataType	   |Telemetry data type. Currently double is supported|
 |    SensorMeasures > Type	  |Measurement type of the sensor telemetry data. Following are the system-defined types: AmbientTemperature, CO2, Depth, ElectricalConductivity, LeafWetness, Length, LiquidLevel, Nitrate, O2, PH, Phosphate, PointInTime, Potassium, Pressure, RainGauge, RelativeHumidity, Salinity, SoilMoisture, SoilTemperature, SolarRadiation, State, TimeDuration, UVRadiation, UVIndex, Volume, WindDirection, WindRun, WindSpeed, Evapotranspiration, PAR. To add more, refer to /ExtendedType API.|
 |        SensorMeasures > Unit	            | Unit of sensor telemetry data. Following are the system-defined units: NoUnit, Celsius, Fahrenheit, Kelvin, Rankine, Pascal, Mercury, PSI, MilliMeter, CentiMeter, Meter, Inch, Feet, Mile, KiloMeter, MilesPerHour, MilesPerSecond, KMPerHour, KMPerSecond, MetersPerHour, MetersPerSecond, Degree, WattsPerSquareMeter, KiloWattsPerSquareMeter, MilliWattsPerSquareCentiMeter, MilliJoulesPerSquareCentiMeter, VolumetricWaterContent, Percentage, PartsPerMillion, MicroMol, MicroMolesPerLiter, SiemensPerSquareMeterPerMole, MilliSiemensPerCentiMeter, Centibar, DeciSiemensPerMeter, KiloPascal, VolumetricIonContent, Liter, MilliLiter, Seconds, UnixTimestamp, MicroMolPerMeterSquaredPerSecond, InchesPerHour To add more, refer to /ExtendedType API.|
-|    SensorMeasures > aggregationType	 |  Values can be none, average, maximum, minimum, or StandardDeviation  |
-|          Name            | Name to identify resource. For example, model name/product name.  |
+|  SensorMeasures > aggregationType	 |  Values can be none, average, maximum, minimum, or StandardDeviation  |
+|        Name            | Name to identify resource. For example, model name/product name.  |
 |    Description        | Provide a meaningful description of the model  |
 |   Properties       |  Additional properties from the manufacturer  |
 |    **Sensor**      |          |
@@ -114,7 +114,7 @@ For more information about objects, see [Swagger](https://aka.ms/FarmBeatsDatahu
 
 **API request to create metadata**
 
-To make an API request, you combine the HTTP (POST) method, the URL to the API service, the URI to a resource to query, submit data to create or delete a request and add one or more HTTP request headers. The URL to the API service is the API Endpoint i.e. the data hub URL `https://\<yourdatahub>.azurewebsites.net`  
+To make an API request, you combine the HTTP (POST) method, the URL to the API service, the URI to a resource to query, submit data to create or delete a request and add one or more HTTP request headers. The URL to the API service is the API Endpoint i.e. the data hub URL <`https://\<yourdatahub>.azurewebsites.net`>  
 
 **Authentication**:
 
@@ -333,7 +333,7 @@ Convert the historical sensor data format to a canonical format that Azure FarmB
 }
 ```
 
-After adding the corresponding devices and sensors, obtain the deviceid and the sensorid in the telemetry message, as described in the previous section
+After adding the corresponding devices and sensors, obtain the deviceid and the sensor id in the telemetry message, as described in the previous section
 
 Example Telemetry message:
 

articles/industry/agriculture/manage-users.md

@@ -1,6 +1,6 @@
 ---
 title: Manage users
-description: Describes how to manage users
+description: This article describes how to manage users.
 author: uhabiba04
 ms.topic: article
 ms.date: 12/02/2019

articles/industry/agriculture/references-for-farmbeats.md

@@ -37,7 +37,7 @@ SensorModel  | SensorModel corresponds to the meta-data of the sensor such as th
 Telemetry  | Telemetry provides the ability to read telemetry messages for a particular sensor and time range.
 Job  | Job corresponds to any workflow of activities, which are executed in the FarmBeats system to get a desired output. Each job is associated with a job ID and job type.
 JobType  | JobType corresponds to different job types supported by the system. This includes system defined & user-defined job types.
-ExtendedType  | ExtendedType corresponds to the list of system & user-defined types in the system. This helps setup a new Sensor or Scene or Scenefile type in the FarmBeats system.
+ExtendedType  | ExtendedType corresponds to the list of system & user-defined types in the system. This helps setup a new Sensor or Scene or Scene file type in the FarmBeats system.
 Partner  | Partner corresponds to the sensor/ imagery integration partner for FarmBeats
 Scene  | Scene corresponds to any generated output in the context of a Farm. Each Scene has a scene ID, scene source, scene type and farm ID associated with it. Each scene ID can have multiple scene files associated with it.
 SceneFile |SceneFile corresponds to all files, which are generated for single scene. A single scene ID can have multiple SceneFile IDs associated with it.

articles/industry/agriculture/troubleshoot-project-farmbeats.md

@@ -15,7 +15,7 @@ For additional help, contact us at [email protected]. Be sure to in
 
 To download the **deployer.log** file, do the following:
 
-1. Sign-in to **Azure Portal** and select your subscription and Azure AD tenant.
+1. Sign-in to **Azure portal** and select your subscription and Azure AD tenant.
 2. Launch Cloud Shell from the top navigation of the Azure portal.
 3. Select **Bash** as the preferred Cloud Shell experience.
 4. Select the highlighted icon and then, in the drop-down list, select **Download**.