redirects4 acro

tarTech23 · tarTech23 · commit f6a8b13103d1 · 2024-04-17T16:19:01.000+03:00
diff --git a/articles/defender-for-iot/device-builders/concept-threadx-security-alerts-recommendations.md b/articles/defender-for-iot/device-builders/concept-threadx-security-alerts-recommendations.md
@@ -11,7 +11,7 @@ Defender-IoT-micro-agent for Eclipse ThreadX continuously analyzes your IoT solu
 
 A Defender-IoT-micro-agent for Eclipse ThreadX alert acts as an indicator of potential compromise, and should be investigated and remediated. A Defender-IoT-micro-agent for Eclipse ThreadX recommendation identifies weak security posture to be remediated and updated. 
 
-In this article, you'll find a list of built-in alerts and recommendations that are triggered based on the default ranges, and customizable with your own values, based on expected or baseline behavior. 
+In this article, you find a list of built-in alerts and recommendations that are triggered based on the default ranges, and customizable with your own values, based on expected or baseline behavior. 
 
 For more information on how alert customization works in the Defender for IoT service, see [customizable alerts](concept-customizable-security-alerts.md). The specific alerts and recommendations available for customization when using the Defender-IoT-micro-agent for Eclipse ThreadX are detailed in the following tables. 
 
@@ -44,8 +44,8 @@ For more information on how alert customization works in the Defender for IoT se
 
 |Device related activity |Alert name  |
 |---------|---------|
-|Active connections|Number of active connections is not in the allowed range|
-|Cloud to device messages in **MQTT** protocol|Number of cloud to device messages in **MQTT** protocol is not in the allowed range|
+|Active connections|Number of active connections isn't in the allowed range|
+|Cloud to device messages in **MQTT** protocol|Number of cloud to device messages in **MQTT** protocol isn't in the allowed range|
 |Outbound connection| Outbound connection to an IP that isn't allowed|
 
 ### Hub related customizable alerts 
diff --git a/articles/defender-for-iot/device-builders/how-to-threadx-security-module.md b/articles/defender-for-iot/device-builders/how-to-threadx-security-module.md
@@ -31,16 +31,16 @@ The default behavior of each configuration is provided in the following tables:
 
 | Name | Type | Default | Details |
 | - | - | - | - |
-| ASC_SECURITY_MODULE_ID | String | defender-iot-micro-agent | The unique identifier of the device.  |
+| 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_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 changes to suspend, if the time is exceeded. |
 
 ## Collection configuration
 
 | Name | Type | Default | Details |
 | - | - | - | - |
-| ASC_FIRST_COLLECTION_INTERVAL | Number  | 30  | The Collector's startup collection interval offset. During startup, the value will be added to the collection of the system in order to avoid sending messages from multiple devices simultaneously.  |
+| ASC_FIRST_COLLECTION_INTERVAL | Number  | 30  | The Collector's startup collection interval offset. During startup, the value is added to the collection of the system in order to avoid sending messages from multiple devices simultaneously. |
 | ASC_HIGH_PRIORITY_INTERVAL | Number | 10 | The collector's high priority group interval (in seconds). |
 | ASC_MEDIUM_PRIORITY_INTERVAL | Number | 30 | The collector's medium priority group interval (in seconds). |
 | ASC_LOW_PRIORITY_INTERVAL | Number | 145,440  | The collector's low priority group interval (in seconds). |
@@ -54,7 +54,7 @@ To customize your collector network activity configuration, use the following:
 | ASC_COLLECTOR_NETWORK_ACTIVITY_TCP_DISABLED | Boolean | false | Filters the `TCP` network activity. |
 | ASC_COLLECTOR_NETWORK_ACTIVITY_UDP_DISABLED | Boolean | false | Filters the `UDP` network activity events. |
 | ASC_COLLECTOR_NETWORK_ACTIVITY_ICMP_DISABLED | Boolean | false | Filters the `ICMP` network activity events. |
-| ASC_COLLECTOR_NETWORK_ACTIVITY_CAPTURE_UNICAST_ONLY | Boolean | true | Captures the unicast incoming packets only. When set to false, it will also capture both Broadcast, and Multicast. |
+| ASC_COLLECTOR_NETWORK_ACTIVITY_CAPTURE_UNICAST_ONLY | Boolean | true | Captures the unicast incoming packets only. When set to false, it captures both Broadcast, and Multicast. |
 | ASC_COLLECTOR_NETWORK_ACTIVITY_SEND_EMPTY_EVENTS  | Boolean  | false  | Sends an empty events of collector. |
 | ASC_COLLECTOR_NETWORK_ACTIVITY_MAX_IPV4_OBJECTS_IN_CACHE | Number | 64 | The maximum number of IPv4 network events to store in memory. |
 | ASC_COLLECTOR_NETWORK_ACTIVITY_MAX_IPV6_OBJECTS_IN_CACHE | Number | 64  | The maximum number of IPv6 network events to store in memory. |
@@ -64,7 +64,7 @@ To customize your collector network activity configuration, use the following:
 | - | - | - | - |
 | ASC_COLLECTOR_HEARTBEAT_ENABLED | Boolean | ON | Enables the heartbeat collector. |
 | ASC_COLLECTOR_NETWORK_ACTIVITY_ENABLED  | Boolean | ON | Enables the network activity collector. |
-| ASC_COLLECTOR_SYSTEM_INFORMATION_ENABLED | Boolean | ON | Enables the system information collector.  |
+| ASC_COLLECTOR_SYSTEM_INFORMATION_ENABLED | Boolean | ON | Enables the system information collector. |
 
 Other configurations flags are advanced, and have unsupported features. Contact support to change this, or for more information.
  
@@ -80,4 +80,4 @@ You can enable and configure Log Analytics to investigate device events and acti
 
 
 - Review and customize Defender-IoT-micro-agent for Eclipse ThreadX [security alerts and recommendations](concept-threadx-security-alerts-recommendations.md)
-- Refer to the [Defender-IoT-micro-agent for Eclipse ThreadX API](azure-threadx-security-module-api.md) as needed.
+- Refer to the [Defender-IoT-micro-agent for Eclipse ThreadX API](threadx-security-module-api.md) as needed.
diff --git a/articles/defender-for-iot/device-builders/threadx-security-module-api.md b/articles/defender-for-iot/device-builders/threadx-security-module-api.md
@@ -80,4 +80,4 @@ Threads
 
 To learn more about how to get started with Eclipse ThreadX Defender-IoT-micro-agent, see the following articles:
 
-- Review the Defender for IoT Eclipse ThreadX Defender-IoT-micro-agent [overview](iot-security-xthread.md).
+- Review the Defender for IoT Eclipse ThreadX Defender-IoT-micro-agent [overview](iot-security-threadx.md).

Original file line number	Diff line number	Diff line change
`@@ -80,4 +80,4 @@ Threads`
`80`	`80`
`81`	`81`	`To learn more about how to get started with Eclipse ThreadX Defender-IoT-micro-agent, see the following articles:`
`82`	`82`
`83`		`-- Review the Defender for IoT Eclipse ThreadX Defender-IoT-micro-agent [overview](iot-security-xthread.md).`
	`83`	`+- Review the Defender for IoT Eclipse ThreadX Defender-IoT-micro-agent [overview](iot-security-threadx.md).`