Update docs/connect/odbc/windows/release-notes-odbc-sql-server-windows.md

Co-authored-by: David Engel <dengel1012@gmail.com>

Author: Theekshna

docs/connect/odbc/windows/release-notes-odbc-sql-server-windows.md

@@ -33,12 +33,16 @@ For the ARM64 driver: [Chinese (Simplified)](https://go.microsoft.com/fwlink/?li
 | ConcatNullYieldsNull property | Added support for ConcatNullYieldsNull property as both a connection string property and a registry key option. |
 | New distribution supported | Added x86 support on Windows ARM64. |
 
-### Known issues
-#### bcp_bind terminator issue
-When we use ‘terminator’ as the separator in bcp_bind for strings, two consecutive terminators in data can mean either NULL value or empty string. ODBC doesn’t have a way to distinguish between empty strings vs null strings.
-- Prior to 18.6.1.1 release, ODBC used to interpret consecutive terminators (0-length data) as empty strings.
-- In 18.6.1.1 release, a change was made to interpret such 0-length data as a NULL value instead of empty string
-In the next ODBC release, we will roll back this change so that we have pre-18.6.1.1 behaviour
+### Known issues in 18.6.1.1
+
+#### Terminator issue in bcp_bind
+
+When a "terminator" is used as the separator in `bcp_bind` for strings, two consecutive terminators in data can mean either a NULL value or an empty string. The ODBC driver doesn’t have a way to distinguish between empty strings and null strings.
+
+- Before the 18.6.1.1 release, the ODBC driver interpreted consecutive terminators (zero-length data) as empty strings.
+- In the 18.6.1.1 release, a change was made to interpret zero-length data as a NULL value instead of an empty string.
+
+This change will be reverted to pre-18.6.1.1 behavior in a future release.
 
 ## Previous Releases