From d55a59e066db6d7e4ffe8efd8f0508fe963f06b3 Mon Sep 17 00:00:00 2001
From: rhjsy-axt <217062081+rhjsy-axt@users.noreply.github.com>
Date: Fri, 4 Jul 2025 09:35:16 +0100
Subject: [PATCH] explicit nvarchar limitation

---
 docs/t-sql/functions/binary-checksum-transact-sql.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/t-sql/functions/binary-checksum-transact-sql.md b/docs/t-sql/functions/binary-checksum-transact-sql.md
index 74a325b2896..410a1dcd17e 100644
--- a/docs/t-sql/functions/binary-checksum-transact-sql.md
+++ b/docs/t-sql/functions/binary-checksum-transact-sql.md
@@ -70,7 +70,7 @@ or
   
 For example, the strings "McCavity" and "Mccavity" have different `BINARY_CHECKSUM` values. In contrast, for a case-insensitive server, `CHECKSUM` returns the same checksum values for those strings. You should avoid comparison of `CHECKSUM` values with `BINARY_CHECKSUM` values.
  
-`BINARY_CHECKSUM` supports any length of type **varbinary(max)** and up to 255 characters of type **nvarchar(max)**.
+`BINARY_CHECKSUM` supports any length of type **varbinary(max)** and up to 255 characters of type **nvarchar(n | max)**.
   
 ## Examples  
 This example uses `BINARY_CHECKSUM` to detect changes in a table row.