Update unsupported-sql-server-features-for-in-memory-oltp.md

Related to https://github.com/MicrosoftDocs/sql-docs/issues/2031

Author: MikeRayMSFT

docs/relational-databases/in-memory-oltp/unsupported-sql-server-features-for-in-memory-oltp.md

@@ -33,7 +33,7 @@ The following [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features
 |Linked Server|You cannot access linked servers in the same query or transaction as memory-optimized tables. For more information, see [Linked Servers (Database Engine)](../../relational-databases/linked-servers/linked-servers-database-engine.md).|  
 |Bulk logging|Regardless of the recovery model of the database, all operations on durable memory-optimized tables are always fully logged.|  
 |Minimal logging|Minimal logging is not supported for memory-optimized tables. For more information about minimal logging, see [The Transaction Log (SQL Server)](../../relational-databases/logs/the-transaction-log-sql-server.md) and [Prerequisites for Minimal Logging in Bulk Import](../../relational-databases/import-export/prerequisites-for-minimal-logging-in-bulk-import.md).|  
-|Change tracking|Change tracking cannot be enabled on a database that contains In-Memory OLTP objects. |
+|Change tracking|Change tracking is not supported for memory optimized tables. |
 | DDL triggers | Neither database-level nor server-level DDL triggers are supported with In-Memory OLTP tables or with natively compiled modules. |  
 | Change Data Capture (CDC) | SQL Server 2017 CU15 and higher support enabling CDC on a database that has memory optimized tables. This is only applicable to the database and any on-disk tables in the database. In earlier versions of SQL Server, CDC cannot be used with a database that has memory-optimized tables, because internally CDC uses a DDL trigger for DROP TABLE. |  
 | Fiber mode | Fiber mode is not supported with memory-optimized tables:<br /><br />If fiber mode is active, you cannot create databases with memory-optimized filegroups, nor can you add memory-optimized filegroups to existing databases.<br /><br />You can enable fiber mode if there are databases with memory-optimized filegroups. However, enabling fiber mode requires a server restart. In that situation, databases with memory-optimized filegroups would fail to recover. Then you would see an error message suggesting that you disable fiber mode to use databases with memory-optimized filegroups.<br /><br />If fiber mode is active, attaching and restoring a databases which has a memory-optimized filegroup fails. The databases would be marked as suspect.<br /><br />For more information, see [lightweight pooling Server Configuration Option](../../database-engine/configure-windows/lightweight-pooling-server-configuration-option.md). |