Apply the background-before-behavior structure to the other CJK docs

locales.rst: state the naming conventions before the two defaults and
name the actual limitation (the script cannot license a Han split)
instead of 'waits for the zh pack'. customize.rst: name the mechanism
behind the opt-out trap (the split still runs; the positional default
then assigns given-first) instead of 'read it twice'. usage.rst: drop
the self-referential lead-in sentence.

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

Author: derek73

docs/customize.rst

@@ -307,11 +307,12 @@ East Asian defaults, and turning them off
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Two defaults key on the *script* a name is written in rather than on
-anything you set: a name written wholly in Han or Hangul reads
+anything you set: a name written wholly in Han or Hangul is assigned
 family-first (``script_orders``), and an unspaced hangul name is split
 into surname and given name against the shipped Korean census list
-(``segment_scripts``). :ref:`east-asian-names` shows what they do —
-this is how to switch them off, which you can do separately:
+(``segment_scripts``). :ref:`east-asian-names` explains the naming
+conventions both rest on — this section is how to switch them off,
+which you can do separately:
 
 .. doctest::
 
@@ -324,10 +325,12 @@ this is how to switch them off, which you can do separately:
     >>> unsplit.parse("김민준").family            # one token, not split
     '김민준'
 
-The middle line is the one to read twice: emptying ``script_orders``
-restores the purely positional reading but leaves the token split, so
-the surname lands in ``given`` instead. Clear both fields to get
-nameparser 2.0's behavior back exactly.
+The two switches interact, and clearing only ``script_orders``
+produces a third behavior rather than the old one: the split still
+runs, so ``김민준`` still becomes two tokens, and the positional
+default then assigns them given-first — the surname lands in
+``given``. To restore nameparser 2.0's reading exactly, clear both
+fields.
 
 To teach the splitter a surname it doesn't ship with, add it to the
 ``surnames`` vocabulary like any other word:

docs/locales.rst

@@ -56,16 +56,22 @@ isn't read as a family name. Listing it in ``given_name_titles`` alone
 raises ``ValueError`` rather than quietly doing nothing.
 
 Two East Asian behaviors are on by default for the same reason, except
-that what selects them is the *script* rather than the word: a name
-written wholly in Han or Hangul reads family-first, and an unspaced
-Korean name is split into surname and given name. Chinese and Japanese
-both write family-first natively, so reading the order takes no guess
-about which language it is; hangul is written by nothing but Korean,
-whose surnames are a closed census set, so splitting is safe too. See
-:ref:`east-asian-names` in :doc:`usage` for what that looks like and
-how to turn either half off. Splitting an unspaced *Han* name is the
-one piece that does need to know the language — a Chinese surname list
-mangles Japanese kanji names — so that half waits for the ``zh`` pack.
+that what selects them is the *script* rather than the word. The
+background (covered fully under :ref:`east-asian-names` in
+:doc:`usage`): Chinese, Japanese, and Korean names put the family name
+first in native script and are usually written with no space between
+the parts. Both defaults follow from facts the script alone
+establishes. A name written wholly in Han or Hangul is assigned
+family-first, because every language written in those scripts orders
+names that way — no language guess is involved. An unspaced hangul
+name is additionally split into surname and given name, because hangul
+is written by nothing but Korean and Korean surnames are a closed
+census set that ships as default vocabulary. Splitting an unspaced
+*Han* name is the one behavior the script cannot license — the same
+characters could be a Chinese or a Japanese name, and a Chinese
+surname list splits Japanese names in the wrong place — so it is not a
+default: the ``zh`` pack below turns it on when you can declare the
+data Chinese.
 
 A pack is for something different: a *structural* rule, like reordering
 a patronymic, that vocabulary alone can't express.

docs/usage.rst

@@ -140,8 +140,7 @@ merging two, and is covered next.
 East Asian names
 -----------------
 
-How these names are built, first, because the parsing rules follow
-from it. A Chinese, Japanese, or Korean name written in its own script
+A Chinese, Japanese, or Korean name written in its own script
 puts the family name first: 毛泽东 is MAO Zedong, 山田太郎 is YAMADA
 Taro, 김민준 is KIM Minjun. The family name is short — one Han
 character or one hangul syllable, occasionally two — and comes from a