Update ad-group-not-discovered.md

Edit review per CI 9082

Author: przlplx

support/mem/configmgr/discovery/ad-group-not-discovered.md

@@ -1,6 +1,6 @@
 ---
 title: Delta AD Group Discovery Doesn't Detect Group Membership Changes in Nested OUs
-description: Troubleshoot an issue in which AD Delta Discovery fails to detect group membership changes in child organizational units.
+description: Troubleshoot an issue in which AD Delta Discovery doesn't detect group membership changes in child organizational units.
 ms.date: 01/12/2025
 ms.reviewer: kaushika, jarrettr, brianhun, payur
 ms.custom: sap:Boundary Groups, Discovery and Collections\Active Directory Discovery (all types)
@@ -17,9 +17,9 @@ This article helps you identify this issue in your environment, and provides wor
 
 ## Symptoms
 
-You set up discovery scopes for Active Directory Group Discovery to target specific Active Directory Domain Services (AD DS) groups as described in [Configure Active Directory Group Discovery](/intune/configmgr/core/servers/deploy/configure/configure-discovery-methods#bkmk_config-adgd). The initial full discovery cycle correctly discovers groups in all the in-scope OUs.
+You set up discovery scopes for AD Group Discovery to target specific Active Directory Domain Services (AD DS) groups, as described in [Configure Active Directory Group Discovery](/intune/configmgr/core/servers/deploy/configure/configure-discovery-methods#bkmk_config-adgd). The initial full discovery cycle correctly discovers groups in all the in-scope OUs.
 
-Later, after the delta discovery cycle runs, you notice that changes in particular group memberships are missed. However, if you force a full discovery cycle to run, the issue resolves as the full discovery cycle discovers changes in all groups in the in-scope OUs.
+After the delta discovery cycle runs, you notice that changes in particular group memberships are missed. However, if you force a full discovery cycle to run, the issue resolves as the full discovery cycle discovers changes in all groups in the in-scope OUs.
 
 In particular, the issue occurs when you define scopes that resemble the following example:
 
@@ -29,20 +29,20 @@ In particular, the issue occurs when you define scopes that resemble the followi
 
 In this example, the delta cycle of AD Group Discovery doesn't detect changes in Group B's membership.
 
-If you want to review log entries to confirm this behavior in your system, see [More information](#more-information).
+If you want to review log entries to verify this behavior in your system, see [More information](#more-information).
 
 ## Cause
 
-During the delta cycle of AD Group Discovery, Configuration Manager detects the organizational units (OUs) of the target groups in the discovery scopes and then builds a tree structure of OUs. It ignores any child OUs of the target groups' OUs.
+During the delta cycle of AD Group Discovery, Configuration Manager detects the OUs of the target groups in the discovery scopes, and then builds a tree structure of OUs. It ignores any child OUs of the OUs in the target groups.
 
 During the full discovery cycle of AD Group Discovery, Configuration Manager uses a different algorithm that doesn't ignore child OUs. Therefore, the discovery process works as expected.
 
 ## Workaround
 
 Microsoft is aware of this issue. To work around this issue, use any of the following methods:
 
-- Move all groups to top-level OUs. For the earlier example, that means moving Group B to another OU that isn't a child of OU-A (or any other OU in the discovery scopes).
-- Reconfigure the discovery scopes to include the child OUs as target OUs. For the earlier example, that means including OU-B in the discovery scopes as an Organizational Unit.
+- Move all groups to top-level OUs. For the earlier example, this action means moving Group B to another OU that isn't a child of OU-A (or of any other OU in the discovery scopes).
+- Reconfigure the discovery scopes to include the child OUs as target OUs. For the previous example, this action means including OU-B in the discovery scopes as an Organizational Unit.
 - Use only the full discovery process for AD Group Discovery.
 
 ## More information