diff --git a/AGENTS.md b/AGENTS.md
index aa04d448..d6097163 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -91,6 +91,12 @@ uv run sphinx-build -b html docs dist/docs
 #    explicitly — every one of them has gone stale at least once.
 #    - docs/*.rst: usage.rst examples and API surface, plus any file listing
 #      config constants or HumanName kwargs
+#    - README.rst's announcement at the top: it is the PyPI project page
+#      (pyproject's `readme`), so it should lead with the release being
+#      shipped, drawn from the release log's summary. 2.4.0 nearly shipped
+#      still announcing 2.0 and 2.1. Check it with `python -m doctest
+#      README.rst` and `uv run --with readme_renderer python -m
+#      readme_renderer README.rst -o /tmp/readme.html` (PyPI's renderer)
 #    - docstrings that autodoc renders (nameparser/_policy.py, _types.py, ...).
 #      These ARE the API reference in modules.html, so a docs/*.rst-only sweep
 #      structurally misses half the rendered page — that is how the guide and
diff --git a/README.rst b/README.rst
index c80cda99..464118e6 100644
--- a/README.rst
+++ b/README.rst
@@ -7,19 +7,25 @@ nameparser parses human names into seven fields — title, given, middle,
 family, suffix, nickname, maiden. Results are immutable, configuration is
 composable, and locale packs are opt-in.
 
-📣 **nameparser 2.0 is out.** Existing ``HumanName`` code keeps working
-through 2.x, and most 1.x code needs no changes. The `migration guide
-<https://nameparser.readthedocs.io/en/latest/migrate.html>`__ has the
-field-by-field map. Please `open an issue
-<https://github.com/derek73/python-nameparser/issues>`__ for anything that
-parses wrong.
-
-**2.1 adds East Asian name support.** Chinese, Japanese and Korean names
-written in their own scripts are read family-first, unspaced Korean names
-are split against the census surname list, and CJK honorifics are
-recognized. See `East Asian names
+📣 **nameparser 2.4 is out.** It uses letter case to read post-nominal
+credentials much more reliably — ``Jack MA`` is Jack with an MA and
+``Jack Ma`` is the surname Ma, and ``Jane Smith, PhD MA`` keeps both
+credentials together — recognizes more naming conventions (Catalan,
+Irish, Finnish, Malay and others), and writes credentials the usual way
+when it repairs case. The `release log
+<https://nameparser.readthedocs.io/en/latest/release_log.html>`__ has the
+details.
+
+Chinese, Japanese and Korean names written in their own scripts are read
+family-first, unspaced Korean names are split against the census surname
+list, and CJK honorifics are recognized. See `East Asian names
 <https://nameparser.readthedocs.io/en/latest/usage.html#east-asian-names>`__.
 
+Existing ``HumanName`` code from 1.x keeps working through 2.x, and most
+of it needs no changes; see `Coming from 1.x`_ below. Please `open an
+issue <https://github.com/derek73/python-nameparser/issues>`__ for anything
+that parses wrong.
+
 Installation
 ------------
 
@@ -52,6 +58,13 @@ Quick Start Example
     >>> name.render("{family}, {given}")
     'de la Vega, Juan'
 
+    >>> parse("Jack MA").suffix                    # capitals mark a credential
+    'MA'
+    >>> parse("Jack Ma").family                    # and a surname
+    'Ma'
+    >>> parse("Jane Smith, PhD MA").suffix
+    'PhD MA'
+
     >>> parse("김민준").family                     # Korean: unspaced, split on the census list
     '김'
     >>> parse("高橋 みなみ").family                 # Japanese: kanji with kana, family first