Merge pull request #199929 from v-dmankowitz/flavor

PRMerger16 · web-flow · commit 3cd17443bd58 · 2022-05-31T22:44:22.000-07:00
Flavor
diff --git a/articles/defender-for-iot/device-builders/concept-micro-agent-configuration.md b/articles/defender-for-iot/device-builders/concept-micro-agent-configuration.md
@@ -53,7 +53,7 @@ These configurations include process, and network activity collectors.
 |--|--|--|--|
 | **Interval** | `High` <br>`Medium`<br>`Low` | Determines the sending frequency.  | `Medium` |
 | **Aggregation mode** | `True` <br>`False` | Determines whether to process event aggregation for an identical event.  | `True` |
-| **Cache size** | cycle FIFO | Defines the number of events collected in between the the times that data is sent. | `256` |
+| **Cache size** | cycle FIFO | Defines the number of events collected in between the times that data is sent. | `256` |
 | **Disable collector** | `True` <br> `False` | Determines whether or not the collector is operational. | `False` |
 | | | | |
 
@@ -67,7 +67,7 @@ These configurations include process, and network activity collectors.
 
 | Setting Name | Setting options | Description | Default |
 |--|--|--|--|
-| **Devices** | A list of the network devices separated by a comma. <br><br>For example `eth0,eth1` | Defines the list of network devices (interfaces) that the agent will use to monitor the traffic. <br><br>If a network device is not listed, the Network Raw events will not be recorded for the missing device.| `eth0` |
+| **Devices** | A list of the network devices separated by a comma. <br><br>For example `eth0,eth1` | Defines the list of network devices (interfaces) that the agent will use to monitor the traffic. <br><br>If a network device isn't listed, the Network Raw events will not be recorded for the missing device.| `eth0` |
 | | | | |
 
 ## Process collector specific-settings
diff --git a/articles/defender-for-iot/device-builders/concept-recommendations.md b/articles/defender-for-iot/device-builders/concept-recommendations.md
@@ -1,6 +1,6 @@
 ---
 title: Security recommendations for IoT Hub 
-description: Learn about the concept of security recommendations and how they are used in the Defender for IoT Hub.
+description: Learn about the concept of security recommendations and how they're used in the Defender for IoT Hub.
 ms.topic: conceptual
 ms.date: 11/09/2021
 ---
diff --git a/articles/defender-for-iot/device-builders/concept-security-module.md b/articles/defender-for-iot/device-builders/concept-security-module.md
@@ -1,6 +1,6 @@
 ---
 title: Defender-IoT-micro-agent and device twins
-description: Learn about the concept of Defender-IoT-micro-agent twins and how they are used in Defender for IoT.
+description: Learn about the concept of Defender-IoT-micro-agent twins and how they're used in Defender for IoT.
 ms.topic: conceptual
 ms.date: 03/28/2022
 ---
diff --git a/articles/defender-for-iot/device-builders/configure-pam-to-audit-sign-in-events.md b/articles/defender-for-iot/device-builders/configure-pam-to-audit-sign-in-events.md
@@ -1,6 +1,6 @@
 ---
 title: Configure Pluggable Authentication Modules (PAM) to audit sign-in events (Preview)
-description: Learn how to configure Pluggable Authentication Modules (PAM) to audit sign-in events when syslog is not configured for your device. 
+description: Learn how to configure Pluggable Authentication Modules (PAM) to audit sign-in events when syslog isn't configured for your device. 
 ms.date: 02/20/2022
 ms.topic: how-to
 ---
diff --git a/articles/defender-for-iot/device-builders/how-to-agent-configuration.md b/articles/defender-for-iot/device-builders/how-to-agent-configuration.md
@@ -41,9 +41,9 @@ If the agent configuration object does not exist in the **azureiotsecurity** mod
 
 ## Configuration schema and validation
 
-Make sure to validate your agent configuration against this [schema](https://aka.ms/iot-security-github-module-schema). An agent will not launch if the configuration object does not match the schema.
+Make sure to validate your agent configuration against this [schema](https://aka.ms/iot-security-github-module-schema). An agent will not launch if the configuration object doesn't match the schema.
 
-If, while the agent is running, the configuration object is changed to a non-valid configuration (the configuration does not match the schema), the agent will ignore the invalid configuration and will continue using the current configuration.
+If, while the agent is running, the configuration object is changed to a non-valid configuration (the configuration doesn't match the schema), the agent will ignore the invalid configuration and will continue using the current configuration.
 
 ### Configuration validation
 
diff --git a/articles/defender-for-iot/device-builders/how-to-azure-rtos-security-module.md b/articles/defender-for-iot/device-builders/how-to-azure-rtos-security-module.md
@@ -30,7 +30,7 @@ The default behavior of each configuration is provided in the following tables:
 | ASC_SECURITY_MODULE_ID | String | defender-iot-micro-agent | The unique identifier of the device.  |
 | SECURITY_MODULE_VERSION_(MAJOR)(MINOR)(PATCH)  | Number | 3.2.1 | The version. |
 | ASC_SECURITY_MODULE_SEND_MESSAGE_RETRY_TIME  | Number  | 3 | The amount of time the Defender-IoT-micro-agent will take to send the security message after a fail. (in seconds) |
-| ASC_SECURITY_MODULE_PENDING_TIME  | Number | 300 | The Defender-IoT-micro-agent pending time (in seconds). The state will change to suspend, if the time is exceeded.. |
+| ASC_SECURITY_MODULE_PENDING_TIME  | Number | 300 | The Defender-IoT-micro-agent pending time (in seconds). The state will change to suspend, if the time is exceeded. |
 
 ## Collection
 
diff --git a/articles/defender-for-iot/device-builders/how-to-deploy-linux-c.md b/articles/defender-for-iot/device-builders/how-to-deploy-linux-c.md
@@ -48,7 +48,7 @@ This script performs the following function:
 
 1. Installs prerequisites.
 
-1. Adds a service user (with interactive sign in disabled).
+1. Adds a service user (with interactive sign-in disabled).
 
 1. Installs the agent as a **Daemon** - assumes the device uses **systemd** for service management.
 
diff --git a/articles/defender-for-iot/device-builders/how-to-deploy-linux-cs.md b/articles/defender-for-iot/device-builders/how-to-deploy-linux-cs.md
@@ -46,7 +46,7 @@ This script performs the following actions:
 
 - Installs prerequisites.
 
-- Adds a service user (with interactive sign in disabled).
+- Adds a service user (with interactive sign-in disabled).
 
 - Installs the agent as a **Daemon** - assumes the device uses **systemd** for legacy deployment model.
 
diff --git a/articles/defender-for-iot/organizations/how-to-connect-sensor-by-proxy.md b/articles/defender-for-iot/organizations/how-to-connect-sensor-by-proxy.md
@@ -25,7 +25,7 @@ The following diagram shows data going from Microsoft Defender for IoT to the Io
 
 ## Set up your system
 
-For this scenario we will be installing, and configuring the latest version of [Squid](http://www.squid-cache.org/) on an Ubuntu 18 server.
+For this scenario we'll be installing, and configuring the latest version of [Squid](http://www.squid-cache.org/) on an Ubuntu 18 server.
 
 > [!Note]
 > Microsoft Defender for IoT does not offer support for Squid or any other proxy service.
diff --git a/articles/defender-for-iot/organizations/how-to-create-and-manage-users.md b/articles/defender-for-iot/organizations/how-to-create-and-manage-users.md
@@ -101,7 +101,7 @@ This section describes how to define users. Cyberx, support, and administrator u
 
 If users aren't active at the keyboard or mouse for a specific time, they're signed out of their session and must sign in again.
 
-When users haven't worked with their console mouse or keyboard for 30 minutes, a session sign out is forced.
+When users haven't worked with their console mouse or keyboard for 30 minutes, a session sign-out is forced.
 
 This feature is enabled by default and on upgrade, but can be disabled. In addition, session counting times can be updated. Session times are defined in seconds. Definitions are applied per sensor and on-premises management console.
 
@@ -203,9 +203,9 @@ You can recover the password for the on-premises management console or the senso
 
 **To recover the password for the on-premises management console, or the sensor**:
 
-1. On the sign in screen of either the on-premises management console or the sensor, select **Password recovery**. The **Password recovery** screen opens.
+1. On the sign-in screen of either the on-premises management console or the sensor, select **Password recovery**. The **Password recovery** screen opens.
 
-    :::image type="content" source="media/how-to-create-and-manage-users/password-recovery.png" alt-text="Screenshot of the Select Password recovery from the sign in screen of either the on-premises management console, or the sensor.":::
+    :::image type="content" source="media/how-to-create-and-manage-users/password-recovery.png" alt-text="Screenshot of the Select Password recovery from the sign-in screen of either the on-premises management console, or the sensor.":::
 
 1. Select either **CyberX** or **Support** from the drop-down menu, and copy the unique identifier code.
 
