Required for a clean commit

Author: memildin

.vscode/settings.json

@@ -57,5 +57,6 @@
     ],
     "cSpell.words": [
         "auditd"
-    ]
+    ],
+    "git.ignoreLimitWarning": true
 }

articles/security-center/security-center-adaptive-network-hardening.md

@@ -23,7 +23,7 @@ Applying [network security groups (NSG)](https://docs.microsoft.com/azure/virtua
 
 Adaptive Network Hardening provides recommendations to further harden the NSG rules. It uses a machine learning algorithm that factors in actual traffic, known trusted configuration, threat intelligence, and other indicators of compromise, and then provides recommendations to allow traffic only from specific IP/port tuples.
 
-For example, let’s say the existing NSG rule is to allow traffic from 140.20.30.10/24 on port 22. The Adaptive Network Hardening’s recommendation, based on the analysis, would be to narrow the range and allow traffic from 140.23.30.10/29 – which is a narrower IP range, and deny all other traffic to that port.
+For example, let's say the existing NSG rule is to allow traffic from 140.20.30.10/24 on port 22. The Adaptive Network Hardening's recommendation, based on the analysis, would be to narrow the range and allow traffic from 140.23.30.10/29 – which is a narrower IP range, and deny all other traffic to that port.
 
 ![network hardening view](./media/security-center-adaptive-network-hardening/traffic-hardening.png)
 
@@ -38,7 +38,7 @@ For example, let’s say the existing NSG rule is to allow traffic from 140.20.3
    * **Unscanned resources**: VMs that the Adaptive Network Hardening algorithm cannot be run on because of one of the following reasons:
       * **VMs are Classic VMs**: Only Azure Resource Manager VMs are supported.
       * **Not enough data is available**: In order to generate accurate traffic hardening recommendations, Security Center requires at least 30 days of traffic data.
-      * **VM is not protected by ASC standard**: Only VMs that are set to Security Center’s Standard pricing tier are eligible for this feature.
+      * **VM is not protected by ASC standard**: Only VMs that are set to Security Center's Standard pricing tier are eligible for this feature.
 
      ![unhealthy resources](./media/security-center-adaptive-network-hardening/unhealthy-resources.png)
 
@@ -74,19 +74,19 @@ You may want to modify the parameters of a rule that has been recommended. For e
 
 Some important guidelines for modifying an Adaptive Network Hardening rule:
 
-* You can modify the parameters of “allow” rules only. 
-* You cannot change “allow” rules to become “deny” rules. 
+* You can modify the parameters of "allow" rules only. 
+* You cannot change "allow" rules to become "deny" rules. 
 
   > [!NOTE]
-  > Creating and modifying “deny” rules is done directly on the NSG. For more information, see [Create, change, or delete a network security group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group).
+  > Creating and modifying "deny" rules is done directly on the NSG. For more information, see [Create, change, or delete a network security group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group).
 
-* A **Deny all traffic** rule is the only type of “deny” rule that would be listed here, and it cannot be modified. You can, however, delete it (see [Delete a rule](#delete-rule)).
+* A **Deny all traffic** rule is the only type of "deny" rule that would be listed here, and it cannot be modified. You can, however, delete it (see [Delete a rule](#delete-rule)).
   > [!NOTE]
-  > A **Deny all traffic** rule is recommended when, as a result of running the algorithm, Security Center does not identify traffic that should be allowed, based on the existing NSG configuration. Therefore, the recommended rule is to deny all traffic to the specified port. The name of this type of rule is displayed as “*System Generated*”. After enforcing this rule, its actual name in the NSG will be a string comprised of the protocol, traffic direction, “DENY”, and a random number.
+  > A **Deny all traffic** rule is recommended when, as a result of running the algorithm, Security Center does not identify traffic that should be allowed, based on the existing NSG configuration. Therefore, the recommended rule is to deny all traffic to the specified port. The name of this type of rule is displayed as "*System Generated*". After enforcing this rule, its actual name in the NSG will be a string comprised of the protocol, traffic direction, "DENY", and a random number.
 
 *To modify an Adaptive Network Hardening rule:*
 
-1. To modify  some of the parameters of a rule, in the **Rules** tab, click on the three dots (...) at the end of the rule’s row, and click **Edit**.
+1. To modify  some of the parameters of a rule, in the **Rules** tab, click on the three dots (...) at the end of the rule's row, and click **Edit**.
 
    ![edit rule](./media/security-center-adaptive-network-hardening/edit-hard-rule.png)
 
@@ -103,10 +103,10 @@ Some important guidelines for modifying an Adaptive Network Hardening rule:
 
 ### Add a new rule <a name ="add-rule"> </a>
 
-You can add an “allow” rule that was not recommended by Security Center.
+You can add an "allow" rule that was not recommended by Security Center.
 
 > [!NOTE]
-> Only “allow” rules can be added here. If you want to add “deny” rules, you can do so directly on the NSG. For more information, see [Create, change, or delete a network security group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group).
+> Only "allow" rules can be added here. If you want to add "deny" rules, you can do so directly on the NSG. For more information, see [Create, change, or delete a network security group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group).
 
 *To add an Adaptive Network Hardening rule:*
 
@@ -130,7 +130,7 @@ When necessary, you can delete a recommended rule for the current session. For e
 
 *To delete an Adaptive Network Hardening rule for your current session:*
 
-1. In the **Rules** tab, click on the three dots (...) at the end of the rule’s row, and click **Delete**.  
+1. In the **Rules** tab, click on the three dots (...) at the end of the rule's row, and click **Delete**.  
 
     ![hardening rules](./media/security-center-adaptive-network-hardening/delete-hard-rule.png)