Improved Acrolinx

Author: w-azure

articles/iot-hub/iot-hub-create-through-portal.md

@@ -42,9 +42,9 @@ Select **Add shared access policy** to open the **Add shared access policy** bla
 
 * The **Registry Read** and **Registry Write** policies grant read and write access rights to the identity registry. These permissions are used by back-end cloud services to manage device identities. Choosing the write option automatically chooses the read option.
 
-* The **Service Connect** policy grants permission to access service endpoints. This permission is used by back-end cloud services to send and receive messages from devices as well as to update and read device twin and module twin data.
+* The **Service Connect** policy grants permission to access service endpoints. This permission is used by back-end cloud services to send and receive messages from devices. It's also used to update and read device twin and module twin data.
 
-* The **Device Connect** policy grants permissions for sending and receiving messages using the IoT Hub device-side endpoints. This permission is used by devices to send and receive messages from an IoT hub, update and read device twin and module twin data, and perform file uploads.
+* The **Device Connect** policy grants permissions for sending and receiving messages using the IoT Hub device-side endpoints. This permission is used by devices to send and receive messages from an IoT hub or update and read device twin and module twin data. It's also used for file uploads.
 
 Select **Add** to add this newly created policy to the existing list.
 
@@ -60,7 +60,7 @@ Select **Message Routing** under **Messaging** to see the Message Routing pane,
 
 ### Routes
 
-Routes is the first tab on the **Message Routing** pane. To add a new route, select **+ Add**. 
+**Routes** is the first tab on the **Message Routing** pane. To add a new route, select **+ Add**. 
 
 ![Message routing pane](./media/iot-hub-create-through-portal/iot-hub-message-routing.png)
 
@@ -105,7 +105,7 @@ Here are two ways to find a specific IoT hub in your subscription:
 
 1. If you know the resource group to which the IoT hub belongs, choose **Resource groups**, then select the resource group from the list. The resource group screen shows all of the resources in that group, including the IoT hubs. Select your hub.
 
-2. Choose **All resources**. On the **All resources** pane, there is a dropdown list that defaults to `All types`. Select the dropdown list, uncheck `Select all`. Find `IoT Hub` and check it. Select the dropdown list box to close it, and the entries will be filtered, showing only your IoT hubs.
+2. Choose **All resources**. On the **All resources** pane, there's a dropdown list that defaults to `All types`. Select the dropdown list, uncheck `Select all`. Find `IoT Hub` and check it. Select the dropdown list box to close it, and the entries will be filtered, showing only your IoT hubs.
 
 ## Delete the IoT hub
 

includes/iot-hub-include-create-device.md

@@ -11,7 +11,7 @@
 ---
 <!-- put the ## header in the file that includes this file -->
 
-In this section, you create a device identity in the identity registry in your IoT hub. A device cannot connect to a hub unless it has an entry in the identity registry. For more information, see the [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md#identity-registry-operations).
+In this section, you create a device identity in the identity registry in your IoT hub. A device can't connect to a hub unless it has an entry in the identity registry. For more information, see the [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md#identity-registry-operations).
 
 1. In your IoT hub navigation menu, open **Devices**, then select **Add Device** to add a device in your IoT hub.
 
@@ -25,7 +25,7 @@ In this section, you create a device identity in the identity registry in your I
 
 1. After the device is created, open the device from the list in the **Devices** pane. Copy the **Primary Connection String**. This connection string is used by device code to communicate with the hub.
 
-    By default, the keys and connection strings are masked as they are sensitive information. If you click the eye icon, they are revealed. It is not necessary to reveal them to copy them with the copy button.
+    By default, the keys and connection strings are masked as they're sensitive information. If you click the eye icon, they're revealed. It's not necessary to reveal them to copy them with the copy button.
 
     :::image type="content" source="./media/iot-hub-include-create-device/device-details.png" alt-text="Screen capture that shows the device connection string" border="true" lightbox="./media/iot-hub-include-create-device/device-details.png":::
 

includes/iot-hub-include-create-hub-cli.md

@@ -55,7 +55,7 @@ If you already have a device registered in your IoT hub, you can skip this secti
 
 To create a device identity:
 
-1. Run the [az iot hub device-identity create](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-create) command in your CLI shell. This creates the device identity.
+1. Run the [az iot hub device-identity create](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-create) command in your CLI shell. This command creates the device identity.
 
     *YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub.
 

includes/iot-hub-include-create-hub.md

@@ -46,14 +46,14 @@ This section describes how to create an IoT hub using the [Azure portal](https:/
 
     - **Pricing and scale tier**: Your selected tier. You can choose from several tiers, depending on how many features you want and how many messages you send through your solution per day. The free tier is intended for testing and evaluation. It allows 500 devices to be connected to the hub and up to 8,000 messages per day. Each Azure subscription can create one IoT hub in the free tier.
 
-      If you are working through a quickstart, select the free tier.
+      If you're working through a quickstart, select the free tier.
 
     - **IoT Hub units**: The number of messages allowed per unit per day depends on your hub's pricing tier. For example, if you want the hub to support ingress of 700,000 messages, you choose two S1 tier units.
     For details about the other tier options, see [Choosing the right IoT Hub tier](../articles/iot-hub/iot-hub-scaling.md).
 
-    - **Microsoft Defender for IoT**: Turn this on to add an extra layer of threat protection to IoT and your devices. This option is not available for hubs in the free tier. Learn more about [security recommendations for IoT Hub in Defender for IoT](../articles/defender-for-iot/device-builders/concept-recommendations.md).
+    - **Microsoft Defender for IoT**: Turn Defender on to add an extra layer of threat protection to IoT and your devices. This option isn't available for hubs in the free tier. Learn more about [security recommendations for IoT Hub in Defender for IoT](../articles/defender-for-iot/device-builders/concept-recommendations.md).
 
-    - **Role-based access control**: Choose how access to the IoT hub is managed, whether shared access policies are allowed or only role-based access control is supported. For more information, see [Control access to IoT Hub by using Azure Active Directory](../articles/iot-hub/iot-hub-dev-guide-azure-ad-rbac.md).
+    - **Role-based access control**: Choose how to manage access to the IoT hub. Allow shared access policies or choose only role-based access control. For more information, see [Control access to IoT Hub by using Azure Active Directory](../articles/iot-hub/iot-hub-dev-guide-azure-ad-rbac.md).
 
     - **Device-to-cloud partitions**: This property relates the device-to-cloud messages to the number of simultaneous readers of the messages. Most hubs need only four partitions.