docs: use dean, not chancellor, as the add-a-title example

chancellor is already in the default TITLES set, so the doctest's
add() was a no-op demonstrating nothing. dean is genuinely absent
(the old v1 docs' example word) -- and absent for a teachable reason,
which the ambiguous-entries paragraph now uses: 'Dean' doubles as a
given name, so a default that swallowed it would misparse
'Dean Martin'.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: derek73

docs/concepts.rst

@@ -52,9 +52,9 @@ this setting vary with?
   ``spec`` you pass to ``render(spec)``, or a keyword to
   ``initials()``/``capitalized()``)
 
-"Chancellor" being a title is a fact about German-language input, not
-about any one dataset or report — that's a :class:`~nameparser.Lexicon`
-entry. A CRM that always exports "Family, Given" strings is a fact
+"Dean" being a title in your data is a fact about the language and
+domain the names come from (academic rosters, say), not about any one
+dataset or report — that's a :class:`~nameparser.Lexicon` entry. A CRM that always exports "Family, Given" strings is a fact
 about that one data source, not about the language of the names in
 it — that's a :class:`~nameparser.Policy`. One particular report
 wanting names formatted as "Family, Given" while every other consumer

docs/customize.rst

@@ -14,9 +14,9 @@ Vocabulary: Lexicon
 .. doctest::
 
     >>> from nameparser import Lexicon, Parser
-    >>> lex = Lexicon.default().add(titles={"chancellor"})
-    >>> Parser(lexicon=lex).parse("Chancellor Angela Merkel").title
-    'Chancellor'
+    >>> lex = Lexicon.default().add(titles={"dean"})
+    >>> Parser(lexicon=lex).parse("Dean Robert Johns").title
+    'Dean'
 
 :meth:`~nameparser.Lexicon.add` and :meth:`~nameparser.Lexicon.remove`
 both return a new :class:`~nameparser.Lexicon` — the one you started
@@ -39,7 +39,11 @@ don't add new vocabulary by themselves; they narrow how an existing
 entry is read when it appears alone. If you're not sure whether a word
 you're adding is one of these ambiguous cases, leave it out — an
 unrecognized word usually still parses reasonably, while a wrongly
-disambiguated one silently picks the less likely reading.
+disambiguated one silently picks the less likely reading. (That
+conservatism is why ``dean`` above isn't in the default vocabulary in
+the first place: "Dean" is also a common given name, and a default
+that swallowed it as a title would misparse "Dean Martin" for
+everyone.)
 
 Behavior: Policy
 -----------------
@@ -145,7 +149,7 @@ you parse.
     # myapp/names.py
     from nameparser import Lexicon, Parser, Policy
 
-    lex = Lexicon.default().add(titles={"chancellor"})
+    lex = Lexicon.default().add(titles={"dean"})
     policy = Policy(strip_emoji=False)
     parser = Parser(lexicon=lex, policy=policy)