diff --git a/docs/ldml/tr35-info.md b/docs/ldml/tr35-info.md
index 21247cb4116..596b942d396 100644
--- a/docs/ldml/tr35-info.md
+++ b/docs/ldml/tr35-info.md
@@ -100,11 +100,11 @@ The CLDR specification is divided into the following parts:
     * [Compute  regions](#compute--regions)
     * [Compute the category](#compute-the-category)
   * [Unit Preferences Data](#Unit_Preferences_Data)
-    * [Examples:](#examples)
+    * [Unit Preferences Data Examples](#unit-preferences-data-examples)
     * [Compute the preferred output unit](#compute-the-preferred-output-unit)
     * [Search the ranked units](#search-the-ranked-units)
   * [Constraints](#constraints)
-    * [Examples](#examples)
+    * [Constraints Examples](#constraints-examples)
 * [Unit APIs](#unit-apis)
 
 ## Introduction <a name="Supplemental_Data" href="#Supplemental_Data">Supplemental Data</a>
@@ -1354,7 +1354,7 @@ Logically, the unit preferences data is a map from categories to a map of usages
 
 **Note:** As of CLDR 37, the `<unitPreference>` `geq` attribute replaces the now-deprecated `<unitPreferences>` `scope` attribute.
 
-#### Examples:
+#### Unit Preferences Data Examples
 
 ```xml
 <unitPreferences category="length" usage="default">
@@ -1437,7 +1437,7 @@ at least 2 significant digits. However, the client can also override or tune the
 * For a given category, usage, and region-set:
   * The `<unitPreference>` elements are in descending order.
 
-#### Examples
+#### Constraints Examples
 
 **Example A: xx-SE-u-ms-metric, length, road**
 1. Fetch the data from `<unitPreferences category="length" usage="road">` for xx-SE
diff --git a/docs/ldml/tr35-modifications.md b/docs/ldml/tr35-modifications.md
index 530f988e099..efa5645ed96 100644
--- a/docs/ldml/tr35-modifications.md
+++ b/docs/ldml/tr35-modifications.md
@@ -21,6 +21,7 @@ For the full header and a general introduction, see [Unicode Common Locale Data
   * [General](#general)
   * [Locales](#locales)
     * [Date and Time](#date-and-time)
+    * [Person Names](#person-names)
     * [MessageFormat](#messageformat)
   * [Numbers](#numbers)
   * [Units](#units)
@@ -84,6 +85,11 @@ and the title of the specification “UTS #35: Unicode Locale Data Markup Langua
 * [`Time_Zone_Goals`](tr35-dates.md#Time_Zone_Goals) Modified the location format construction.
 * [`Time Zone Format Terminology`](tr35-dates.md#Time_Zone_Format_Terminology) Clarified the computation of the exemplar city for non-location zones.
 
+#### Person Names
+
+* [initialPattern Syntax](tr35-personNames.md#initialpattern-syntax), [sampleName Syntax](tr35-personNames.md#samplename-syntax) Retitled the two “Syntax” headings after their sections, so that each one has its own link.
+<!-- CLDR-19840 -->
+
 #### MessageFormat
 
 * [:currency](tr35-messageFormat.md#the-currency-function), [:percent](tr35-messageFormat.md#the-percent-function) The `:currency` and `:percent` functions are now Stable, with the same implementations as previously.
@@ -105,6 +111,8 @@ and the title of the specification “UTS #35: Unicode Locale Data Markup Langua
 
 * [Unit Preferences Data](tr35-info.md#Unit_Preferences_Data) Made formatting and phrasing more internally consistent
 <!-- CLDR-19737 -->
+* [Unit Preferences Data Examples](tr35-info.md#unit-preferences-data-examples), [Constraints Examples](tr35-info.md#constraints-examples) Retitled the two “Examples” headings after their sections, so that each one has its own link.
+<!-- CLDR-19840 -->
 
 ### Collation
 
diff --git a/docs/ldml/tr35-personNames.md b/docs/ldml/tr35-personNames.md
index 1788bdc85d0..19bb2b3a486 100644
--- a/docs/ldml/tr35-personNames.md
+++ b/docs/ldml/tr35-personNames.md
@@ -64,7 +64,7 @@ The CLDR specification is divided into the following parts:
   * [foreignSpaceReplacement Element](#foreignspacereplacement-element)
   * [nativeSpaceReplacement Element](#nativespacereplacement-element)
   * [initialPattern Element](#initialpattern-element)
-    * [Syntax](#syntax)
+    * [initialPattern Syntax](#initialpattern-syntax)
 * [Person Name Object](#person-name-object)
 * [Person Name Attributes](#person-name-attributes)
   * [order](#order)
@@ -93,7 +93,7 @@ The CLDR specification is divided into the following parts:
     * [Examples of space replacement](#examples-of-space-replacement)
   * [Formatting examples](#formatting-examples)
 * [Sample Name](#sample-name)
-  * [Syntax](#syntax)
+  * [sampleName Syntax](#samplename-syntax)
   * [Expected values](#expected-values)
 * [Person Name Validation](#person-name-validation)
   * [Letters](#letters)
@@ -330,7 +330,7 @@ The `<initialPattern>` element is used to specify how to format initials of name
 
 **_initial_** is a pattern used to display a single initial in the locale, while **_initialSequence_** is a pattern used to “glue” together multiple initials for multiword fields, for example with the given name “Mary Beth” in English.
 
-#### Syntax
+#### initialPattern Syntax
 
 ```xml
 <!ELEMENT initialPattern ( #PCDATA ) >
@@ -1080,7 +1080,7 @@ The output is:
 The sampleName element is used for test names in the personNames CLDR XML data for each locale to aid in testing and display in the CLDR Survey Tool.
 They are not intended to be used in production software as prompts or placeholders in a user interface and should not be displayed in a user interface.
 
-### Syntax
+### sampleName Syntax
 
 ```xml
 <!ELEMENT sampleName ( nameField+ )  >