Update docs/relational-databases/sql-server-transaction-log-architecture-and-management-guide.md

PiJoCoder · rwestMSFT · web-flow · commit aabd4264aca1 · 2023-11-30T11:31:40.000-06:00
Co-authored-by: Randolph West MSFT &lt;97149825+rwestMSFT@users.noreply.github.com&gt;
diff --git a/docs/relational-databases/sql-server-transaction-log-architecture-and-management-guide.md b/docs/relational-databases/sql-server-transaction-log-architecture-and-management-guide.md
@@ -107,7 +107,8 @@ During the initial stages of a database recovery process, SQL Server discovers a
 - Attempts to attach a database take a very long time to complete.
 - When you try to set up database mirroring, you encounter error messages 1413, 1443, and 1479, indicating a timeout.
 - You encounter memory-related errors like 701 when you attempt to restore a database.
-- Transactional replication or Change Data Capture may experience significant latency
+- Transactional replication or change data capture may experience significant latency.
+
 
 When you examine the SQL Server Error log, you may notice that a significant amount of time is spent before the *analysis* phase of the database recovery process.
 For example:
