adding to TOC and reference docs

Author: PiJoCoder

docs/relational-databases/errors-events/includes/sql-server-2016-database-engine-events-and-errors-18000-18999.md

@@ -8,7 +8,7 @@ ms.topic: include
 | :--- | :--- | :--- | :--- |
 | 18002 | 20 | Yes | Exception happened when running extended stored procedure '%.\*ls' in the library '%.\*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. To generate a minidump, create an xevent session using the dump routine event with the create dump action. |
 | 18052 | 16 | No | Error: %d, Severity: %d, State: %d. |
-| 18053 | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
+| [18053](../mssqlserver-18053-database-engine-error.md) | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
 | 18054 | 16 | Yes | Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. |
 | 18055 | 20 | Yes | Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support. |
 | 18056 | 20 | Yes | The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. |

docs/relational-databases/errors-events/includes/sql-server-2017-database-engine-events-and-errors-18000-18999.md

@@ -8,7 +8,7 @@ ms.topic: include
 | :--- | :--- | :--- | :--- |
 | 18002 | 20 | Yes | Exception happened when running extended stored procedure '%.\*ls' in the library '%.\*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. To generate a minidump, create an xevent session using the dump routine event with the create dump action. |
 | 18052 | 16 | No | Error: %d, Severity: %d, State: %d. |
-| 18053 | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
+| [18053](../mssqlserver-18053-database-engine-error.md) | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
 | 18054 | 16 | Yes | Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. |
 | 18055 | 20 | Yes | Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support. |
 | 18056 | 20 | Yes | The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. |

docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-18000-18999.md

@@ -8,7 +8,7 @@ ms.topic: include
 | :--- | :--- | :--- | :--- |
 | 18002 | 20 | Yes | Exception happened when running extended stored procedure '%.\*ls' in the library '%.\*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. To generate a minidump, create an xevent session using the dump routine event with the create dump action. |
 | 18052 | 16 | No | Error: %d, Severity: %d, State: %d. |
-| 18053 | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
+| [18053](../mssqlserver-18053-database-engine-error.md) | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
 | 18054 | 16 | Yes | Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. |
 | 18055 | 20 | Yes | Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support. |
 | 18056 | 20 | Yes | The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-18000-18999.md

@@ -8,7 +8,7 @@ ms.topic: include
 | :--- | :--- | :--- | :--- |
 | 18002 | 20 | Yes | Exception happened when running extended stored procedure '%.\*ls' in the library '%.\*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. To generate a minidump, create an xevent session using the dump routine event with the create dump action. |
 | 18052 | 16 | No | Error: %d, Severity: %d, State: %d. |
-| 18053 | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
+| [18053](../mssqlserver-18053-database-engine-error.md) | 16 | No | Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. |
 | 18054 | 16 | Yes | Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. |
 | 18055 | 20 | Yes | Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support. |
 | 18056 | 20 | Yes | The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. |

docs/relational-databases/errors-events/mssqlserver-18053-database-engine-error.md

@@ -28,7 +28,7 @@ helpviewer_keywords:
 
 ## Explanation
 
-You might receive error 18053 in the SQL Server Error Log or at run time. Here are examples of how you can see this error:
+You might receive error 18053 in the SQL Server Error Log or at run time. Here is an example of how you can see this error:
 
 ```output
 Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

docs/toc.yml

@@ -11711,6 +11711,8 @@ items:
         items:
         - name: Overview
           href: relational-databases/errors-events/database-engine-events-and-errors-18000-to-18999.md
+        - name: 18053
+          href: relational-databases/errors-events/mssqlserver-18053-database-engine-error.md
         - name: 18210
           href: relational-databases/errors-events/mssqlserver-18210-database-engine-error.md
         - name: 18264