minor updates

Author: sevend2

support/sql/database-engine/database-file-operations/error-3853-use-incremental-statistics-resumable-index-operations.md

@@ -1,6 +1,6 @@
 ---
 title: Error 3853 When Using Incremental Statistics And Resumable Index Operations
-description: This article helps you resolve SQL Server error 3853 that occurs when you use incremental statistics and resumable index operations concurrently.
+description: Resolve SQL Server error 3853 that occurs when you use incremental statistics and resumable index operations concurrently.
 ms.date: 03/19/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
 ms.reviewer: rtownsend
@@ -31,26 +31,26 @@ Msg 3853, Level 16, State 1, Line 10
 
 ## Cause
 
-The 3853 error is caused by orphaned records under the `sys.syssingleobjrefs` system table. The `stats_id` in `sys.stats` is still `2`, while it's `896002` in `syssingleobjrefs`. The issue occurs under the following scenarios:
+The 3853 error is caused by orphaned records in the `sys.syssingleobjrefs` system table. The `stats_id` in `sys.stats` remains as `2`, while while the corresponding `stats_id` in `syssingleobjrefs` is `896002`, indicating a mismatch. The issue occurs under the following scenarios:
 
 - The source `object_id` is a partitioned table or index.
-- Incremental statistics are in use for table or index.
-- Index create or rebuild is performed using the **RESUMABLE** option.
-- Incremental statistics are updated or the index is rebuilt online.
+- Incremental statistics are in use for a table or index.
+- Index creation or rebuild is performed using the **RESUMABLE** option.
+- Incremental statistics are updated or the index is rebuilt using the `ONLINE = ON` option.
 
 ## Status
 
-Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the [Applies to](#applies-to) section.  Microsoft has also confirmed that the issue is fixed in [Microsoft SQL Server 2022](https://www.microsoft.com/sql-server/sql-server-downloads).
+Microsoft has confirmed that this is a known issue in the versions of SQL Server listed in the [Applies to](#applies-to) section.  Microsoft has also confirmed that the issue has been fixed in [Microsoft SQL Server 2022](https://www.microsoft.com/sql-server/sql-server-downloads).
 
 ## Resolution
 
 If the issue occurs, try the following options:
 
 - Contact the Microsoft Customer Support team to request assistance with correcting the metadata.
 - Restore the database from the most recent valid backup.
-- Create a new database and import the data from the corrupted database using data import or export tools or manual export-import methods.
+- Create a new database and import the data from the corrupted database using SQL Server Import and Export Wizard, BCP utility, or manual export-import methods.
 - Upgrade to SQL Server 2022 where the issue has been fixed.
 
 ## Workaround
 
-To avoid this issue, don't use incremental statistics and resumable index operations simultaneously.
+To avoid this issue, refrain from using incremental statistics and resumable index operations on the same table or index simultaneously.