From 200129f164bc3893b35914e457c9b97f131524e5 Mon Sep 17 00:00:00 2001
From: finnigd <138986077+finnigd@users.noreply.github.com>
Date: Wed, 9 Apr 2025 19:35:41 +1200
Subject: [PATCH] Correct typo - should be maxscans

Correct typo - should be maxscans, not maxtrans, in the one-shot description.
---
 .../administer-and-monitor-change-data-capture-sql-server.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/relational-databases/track-changes/administer-and-monitor-change-data-capture-sql-server.md b/docs/relational-databases/track-changes/administer-and-monitor-change-data-capture-sql-server.md
index 5a8eae61e02..d2947af96b5 100644
--- a/docs/relational-databases/track-changes/administer-and-monitor-change-data-capture-sql-server.md
+++ b/docs/relational-databases/track-changes/administer-and-monitor-change-data-capture-sql-server.md
@@ -43,7 +43,7 @@ The `continuous` parameter controls whether `sp_cdc_scan` relinquishes control i
   
 ##### One-shot mode
 
-In one-shot mode, the capture job requests `sp_cdc_scan` to perform up to `maxtrans` scans to try to drain the log and return. Any transactions in addition to `maxtrans` that are present in the log will be processed in later scans.  
+In one-shot mode, the capture job requests `sp_cdc_scan` to perform up to `maxscans` scans to try to drain the log and return. Any transactions in addition to `maxtrans` that are present in the log will be processed in later scans.  
   
  One-shot mode is used in controlled tests, where the volume of transactions to be processed is known, and there are advantages to the fact that the job closes automatically on when it is finished. One-shot mode is not recommended for production use. This is because it relies on the job schedule to manage how frequently the scan cycle is run.