Merge pull request #109465 from uhabiba04/master

updated as per microsoft doc standards

Author: ttorble

articles/industry/agriculture/get-sensor-data-from-sensor-partner.md

@@ -32,51 +32,53 @@ After you start the streaming of sensor data, you can begin the process of getti
  - Client secret
  - EventHub connection string
 
-You can generate the above information by following these steps: (Please note these steps are required to be done on Azure so you will need access to the Azure subscription where FarmBeats is deployed)
+Follow the below steps to  generate the above information:
+
+> [!NOTE]
+> These steps are required to be completed on Azure to access the Azure
+> subscription where FarmBeats is deployed.
 
 1. Sign in to https://portal.azure.com/.
 
-2. **If you are on FarmBeats version 1.2.7 or later, please skip steps 2a, 2b and 2c, and go to step 3.**. You can check FarmBeats version by clicking on the Settings icon on the top-right side of the FarmBeats UI.
+2. **If you are on FarmBeats version 1.2.7 or later, skip steps a, b and c, and go to step 3.** You can check FarmBeats version by selecting the **Settings** icon on the top-right corner of the FarmBeats UI.
 
-2a. Go to Azure Active Directory -> App Registrations
+      a.  Go to **Azure Active Directory** > **App Registrations**
 
-2b. Click on the App Registration that was created as part of your FarmBeats deployment. It will have the same name as your FarmBeats data hub.
+      b. Select the **App Registration** that was created as part of your FarmBeats deployment. It will have the same name as your FarmBeats datahub.
 
-2c. Click on “Expose an API” -> Click “Add a client application” and enter **04b07795-8ddb-461a-bbee-02f9e1bf7b46** and check "Authorize Scope". This will give access to the Azure CLI (Cloud Shell) to perform the below steps.
+      c. Select **Expose an API** > select **Add a client application** and enter **04b07795-8ddb-461a-bbee-02f9e1bf7b46** and check **Authorize Scope**. This will give access to the Azure CLI (Cloud Shell) to perform the below steps:
 
 3. Open Cloud Shell. This option is available on the toolbar in the upper-right corner of the Azure portal.
 
     ![Azure portal toolbar](./media/get-drone-imagery-from-drone-partner/navigation-bar-1.png)
 
-5. Make sure the environment is set to **PowerShell**. By default, it's set to Bash.
+4. Ensure the environment is set to **PowerShell**. By default, it's set to Bash.
 
     ![PowerShell toolbar setting](./media/get-sensor-data-from-sensor-partner/power-shell-new-1.png)
 
-6. Go to your home directory.
-
-   ```azurepowershell-interactive 
+5. Go to your home directory.
 
+    ```azurepowershell-interactive 
     cd  
-
     ```
 
-7. Run the following command. This will download a script to your home directory.
+6. Run the following command. This will download a script to your home directory.
 
     ```azurepowershell-interactive 
 
-    wget –q https://aka.ms/farmbeatspartnerscriptv3 -O ./generatePartnerCredentials.ps1 
+    wget –q https://aka.ms/farmbeatspartnerscriptv3 -O ./generatePartnerCredentials.ps1
 
     ```
 
-8. Run the following script. The script asks for the Tenant ID which can be obtained from Azure Active Directory -> Overview page.
+7. Run the following script. The script asks for the Tenant ID, which can be obtained from **Azure Active Directory** > **Overview** page.
 
     ```azurepowershell-interactive 
 
     ./generatePartnerCredentials.ps1   
 
     ```
 
-9. Follow the onscreen instructions to capture the values for **API Endpoint**, **Tenant ID**, **Client ID**, **Client Secret**, and **EventHub Connection String**.
+8. Follow the onscreen instructions to capture the values for **API Endpoint**, **Tenant ID**, **Client ID**, **Client Secret**, and **EventHub Connection String**.
 
 ### Integrate device data by using the generated credentials
 
@@ -86,16 +88,16 @@ Now you have the following information generated from the previous section.
  - Client ID
  - Client secret
  - Tenant ID
- 
-You will need to provide this to your device partner for linking FarmBeats. Go to the device partner portal for doing the same. For example, in case you are using devices from Davis Instruments, Teralytic or Pessl Instruments (Metos.at) please go to the corresponding pages as mentioned below:
 
-[Davis Instruments](https://weatherlink.github.io/azure-farmbeats/setup)
+You will need to provide this to your device partner for linking FarmBeats. Go to the device partner portal for doing the same. For example, in case you are using devices from Davis Instruments, Teralytic or Pessl Instruments (Metos.at) go to the corresponding pages as mentioned below:
+
+1. [Davis Instruments](https://weatherlink.github.io/azure-farmbeats/setup)
 
-[Teralytic](https://app.teralytic.com/)
+2. [Teralytic](https://app.teralytic.com/)
 
-[Pessl Instruments](https://ng.fieldclimate.com/user-api-services)
+3. [Pessl Instruments](https://ng.fieldclimate.com/user-api-services)
 
- The device provider confirms a successful integration. Upon confirmation, you can view all the devices and sensors on Azure FarmBeats.
+The device provider confirms a successful integration. Upon confirmation, you can view all the devices and sensors on Azure FarmBeats.
 
 ## View devices and sensors
 
@@ -108,7 +110,7 @@ Currently, FarmBeats supports the following devices:
 - **Node**: A device to which one or more sensors are attached.
 - **Gateway**: A device to which one or more nodes are attached.
 
-Follow these steps.
+Follow these steps:
 
 1. On the home page, select **Devices** from the menu.
   The **Devices** page displays the device type, model, status, the farm it's placed in, and the last updated date for metadata. By default, the farm column is set to *NULL*. You can choose to assign a device to a farm. For more information, see [Assign devices](#assign-devices).
@@ -118,7 +120,7 @@ Follow these steps.
 
 ### View sensors
 
-Follow these steps.
+Follow these steps:
 
 1. On the home page, select **Sensors** from the menu.
   The **Sensors** page displays details about the type of sensor, the farm it's connected to, parent device, port name, port type, and the last updated status.
@@ -142,11 +144,12 @@ After the sensor data is flowing in, you can assign it to the farm where you dep
     ![Associate Devices window](./media/get-sensor-data-from-sensor-partner/associate-devices-1.png)
 
 6. To associate each device to a different farm, select the drop-down arrow in the **Assign to Farm** column, and select a farm for each device row.
+
 7. Select **Assign** to complete the device assignment.
 
 ### Visualize sensor data
 
-Follow these steps.
+Follow these steps:
 
 1. On the home page, select **Farms** from the menu to view the **Farms** page.
 2. Select the **Farm** for which you want to see the sensor data.
@@ -156,7 +159,7 @@ Follow these steps.
 
 ## Delete a sensor
 
-Follow these steps.
+Follow these steps:
 
 1. On the home page, select **Sensors** from the menu to view the **Sensors** page.
 2. Select the device you want to delete, and select **Delete** in the confirmation window.
@@ -167,7 +170,7 @@ A confirmation message shows that the sensor is successfully deleted.
 
 ## Delete devices
 
-Follow these steps.
+Follow these steps:
 
 1. On the home page, select **Devices** from the menu to view the **Devices** page.
 2. Select the device you want to delete, and select **Delete** in the confirmation window.