Update prereqs-restrictions-recommendations-always-on-availability.md

SQLSourabh · web-flow · commit de5db5c6cf4c · 2019-01-31T15:23:47.000-08:00
updated statement around parallel redo mode and thread assignment.
diff --git a/docs/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md b/docs/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md
@@ -2,7 +2,7 @@
 title: "Prerequisites, Restrictions, and Recommendations for availability groups"
 description: "A description of the prerequisites, restrictions and recommendations for deploying an Always On availability group."
 ms.custom: "seodec18"
-ms.date: "06/05/2018"
+ms.date: "01/31/2019"
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: high-availability
@@ -154,7 +154,7 @@ manager: craigg
     -   A SQL Server instance uses up to 100 threads for parallel redo for secondary replicas. Each database uses up to one-half of the total number of CPU cores, but not more than 16 threads per database. If the total number of required threads for a single instance exceeds 100, SQL Server uses a single redo thread for every remaining database. Serial Redo threads are released after ~15 seconds of inactivity. 
     
     > [!NOTE]
-    > Databases are chosen to go single-threaded based on their ascending database ID. As such, the database creation order should be considered for SQL Server instances that host more availability group databases than available worker threads. For example, on a system with 32 or more CPU cores, all databases starting with the 7th database that joined the availability group will be in serial redo mode irrespective of the actual redo workload for each database. Databases that require parallel redo should be added to the availability group first.    
+    > Databases are chosen to go single-threaded based on their ascending database ID. As such, the database creation order should be considered for SQL Server instances that host more availability group databases than available worker threads. For example, on a system with 32 or more CPU cores, the first six databases (ordered by database ID) in an availability group or groups will use parallel redo mode, and all subsequent databases will use single redo mode.
   
 -   In addition, availability groups use unshared threads, as follows:  
   
