docs: comma-order example a reader can verify without cultural context

'Yamamoto, Haruki' only demonstrates the point if you already know
which word is the surname. 'Thomas, John' is ambiguous to an
English-reading audience in exactly the way the comma resolves.

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

Author: derek73

docs/customize.rst

@@ -65,8 +65,8 @@ listed below.
      - Assigns positional (no-comma) input to given/middle/family in
        this order. Use the exported ``GIVEN_FIRST`` (default),
        ``FAMILY_FIRST``, or ``FAMILY_FIRST_GIVEN_LAST`` constants.
-       Ignored for comma-format input ("Yamamoto, Haruki"), which
-       states its own order.
+       Ignored for comma-format input — the comma itself states the
+       order ("Thomas, John" puts the family name first).
    * - ``patronymic_rules``
      - ``frozenset[PatronymicRule]``
      - Reorders patronymic-shaped names via opt-in detectors — East

nameparser/_policy.py

@@ -77,9 +77,10 @@ class Policy:
     #: :ref:`name-order constants <name-order-constants>` --
     #: GIVEN_FIRST (the default), FAMILY_FIRST, and
     #: FAMILY_FIRST_GIVEN_LAST; any other tuple of Roles raises
-    #: ValueError. Ignored when the input contains a comma:
-    #: comma-format input ("Yamamoto, Haruki") states its own order
-    #: explicitly.
+    #: ValueError. Ignored when the input contains a comma: the comma
+    #: itself states the order -- "Thomas, John" puts the family name
+    #: first no matter which words could otherwise be either
+    #: ("Thomas" and "John" both work as given or family names).
     name_order: tuple[Role, Role, Role] = GIVEN_FIRST
     #: Opt-in detectors that reorder patronymic-shaped names
     #: (EAST_SLAVIC, TURKIC); usually set via a locale pack.