Merge pull request #18050 from David-Engel/patch-3

PRMerger18 · web-flow · commit 6b0de80d54fd · 2020-12-08T13:48:38.000-08:00
Link directly to locking in the database engine
diff --git a/docs/connect/jdbc/understanding-row-locking.md b/docs/connect/jdbc/understanding-row-locking.md
@@ -2,7 +2,7 @@
 description: "Understanding row locking"
 title: "Understanding row locking | Microsoft Docs"
 ms.custom: ""
-ms.date: "08/12/2019"
+ms.date: "12/08/2020"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -25,7 +25,7 @@ The [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] uses [!INCLUDE
 Locking is used to assure transactional integrity and database consistency. Locking prevents users from reading data that is being changed by other users, and prevents multiple users from changing the same data at the same time. If locking is not used, data within the database might become logically incorrect, and queries run against that data might produce unexpected results.
 
 > [!NOTE]  
-> For more information about row locking in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], see "Locking in the [!INCLUDE[ssDE](../../includes/ssde_md.md)]" in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Books Online.
+> For more information about row locking in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], see ["Locking in the [!INCLUDE[ssDE](../../includes/ssde_md.md)]"](../../relational-databases/sql-server-transaction-locking-and-row-versioning-guide.md#Lock_Engine) in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Books Online.
 
 ## See also
 
