20231002 anchor link

WilliamDAssafMSFT · WilliamDAssafMSFT · commit 2a43a1187e7a · 2023-10-02T13:35:08.000-07:00
diff --git a/docs/relational-databases/security/row-level-security.md b/docs/relational-databases/security/row-level-security.md
@@ -150,7 +150,7 @@ It is possible to cause information leakage by using carefully crafted queries t
 
 - **PolyBase:** RLS is supported with external tables in Azure Synapse and SQL Server 2019 CU7 or higher versions.
 
-- **Memory-Optimized Tables:** The inline table-valued function used as a security predicate on a memory-optimized table must be defined using the `WITH NATIVE_COMPILATION` option. With this option, language features not supported by memory-optimized tables will be banned and the appropriate error will be issued at creation time. For more information, see [Row-level security in Memory-Optimized Tables](../../relational-databases/in-memory-oltp/introduction-to-memory-optimized-tables.md#row-level-security-in-memory-optimized-tables).
+- **Memory-Optimized Tables:** The inline table-valued function used as a security predicate on a memory-optimized table must be defined using the `WITH NATIVE_COMPILATION` option. With this option, language features not supported by memory-optimized tables will be banned and the appropriate error will be issued at creation time. For more information, see [Row-level security in Memory-Optimized Tables](../../relational-databases/in-memory-oltp/introduction-to-memory-optimized-tables.md#rls).
 
 - **Indexed views:** In general, security policies can be created on top of views, and views can be created on top of tables that are bound by security policies. However, indexed views cannot be created on top of tables that have a security policy, because row lookups via the index would bypass the policy.
 
