Merge pull request #10550 from v-tappelgate/AB#9349-Summary-updates

AB#9349: Summary updates

Author: v-tappelgate

support/windows-server/active-directory/adamsync-cant-sync-basedn-grandchild-ou.md

@@ -16,10 +16,14 @@ appliesto:
 
 # Endless loop in AD DS to AD LDS synchronization if base DN is a grandchild OU
 
-This article discusses how to work around a behavior in the Active Directory Application Mode (ADAM) Synchronizer (Adamsync) tool. This behavior causes the synchronization process to enter an endless loop if the base distinguished name (base DN) is a grandchild OU. You can stop the loop only by using Task Manager or by pressing Ctrl+C.
-
 _Original KB number:_   926933
 
+## Summary
+
+When you use the Active Directory Application Mode (ADAM) Synchronizer (Adamsync) tool to synchronize data from Active Directory Domain Services (AD DS) to Active Directory Lightweight Directory Services (AD LDS), the synchronization process might enter an endless loop. This issue occurs when you specify a grandchild organizational unit (OU) as the base distinguished name (base DN) in the Adamsync configuration file.
+
+This article describes the symptoms, cause, and workarounds for this known issue in the Adamsync tool.
+
 ## Symptoms
 
 You have an Active Directory Domain Services (AD DS) forest and an Active Directory Lightweight Directory Service (AD LDS) instance. You use the Adamsync tool in Windows to synchronize data from the AD DS forest to the AD LDS instance. However, the synchronization never finishes. For a detailed walkthrough of this process, see [More information](#more-information).

support/windows-server/backup-and-storage/delete-s2d-storage-pool-reuse-disks.md

@@ -14,7 +14,18 @@ appliesto:
 ---
 # Delete a Storage Spaces Direct storage pool and reset the physical disks
 
-This article uses an example Storage Spaces Direct (S2D) deployment to explain how to gracefully delete an S2D storage pool. This process cleans S2D information from the disks that the storage pool aggregates so that you can reuse the disks elsewhere. If you use a different approach to remove disks from a storage pool, both the disks and the storage pool might enter an unusable state. For more information about these issues and related events, see [More information](#more-information).
+## Summary
+
+This article describes how to safely remove a Storage Spaces Direct (S2D) storage pool and prepare the physical disks for reuse. Follow these steps to avoid rendering the disks or storage pool unusable.
+
+When you remove disks from a storage pool incorrectly, both the disks and the storage pool can enter an unusable state. This article provides a step-by-step procedure to gracefully delete an S2D storage pool and clean the disks so that you can reuse them in a different configuration. For more information about these issues and related events, see [More information](#more-information).
+
+> [!CAUTION]  
+> Make sure that you back up any data that's in the storage pool. The steps in this article delete all data from the disks.
+
+The steps in this article don't affect the  current Windows Server Failover Cluster (WSFC) configuration. These steps modify only the S2D configuration.
+
+## Introduction to the example
 
 This example uses the following steps to completely remove the S2D configuration and prepare the disks for reuse:
 
@@ -25,8 +36,6 @@ This example uses the following steps to completely remove the S2D configuration
 1. [Verify that everything is removed](#step-5-verify-that-everything-is-removed).
 1. [Clean up the physical disks](#step-6-clean-up-the-physical-disks).
 
-The current Windows Server Failover Cluster (WSFC) configuration isn't changed. These steps modify only the S2D configuration.
-
 The example in this section uses the following configuration:
 
 - **S2D on S2DclusterNew**: S2D storage pool. It includes two virtual disks that host volumes (ClusterPerformanceHistory and userdata01)