From f1d39547e9f55bd42304488122fd5e7c952a2db5 Mon Sep 17 00:00:00 2001
From: Alex <100605452+Likio3000@users.noreply.github.com>
Date: Wed, 23 Sep 2026 07:38:02 +1000
Subject: [PATCH] docs: identify camelCase in the ambiguous-character option
 guidance

---
 packages/change-case/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/change-case/README.md b/packages/change-case/README.md
index 9085c9b6..f1d2cce1 100644
--- a/packages/change-case/README.md
+++ b/packages/change-case/README.md
@@ -43,7 +43,7 @@ All methods accept an `options` object as the second argument:
 - `prefixCharacters?: string` Retain at the beginning of the string. Defaults to `""`. Example: use `"_"` to keep the underscores in `__typename`.
 - `suffixCharacters?: string` Retain at the end of the string. Defaults to `""`. Example: use `"_"` to keep the underscore in `type_`.
 
-By default, `pascalCase` and `snakeCase` separate ambiguous characters with `_`. For example, `V1.2` would become `V1_2` instead of `V12`. If you prefer them merged you can set `mergeAmbiguousCharacters` to `true`.
+By default, `pascalCase` and `camelCase` separate ambiguous characters with `_`. For example, `pascalCase("V1.2")` returns `V1_2` instead of `V12`. If you prefer them merged you can set `mergeAmbiguousCharacters` to `true`.
 
 ### Split