diff --git a/spec/appendices.md b/spec/appendices.md
index b65036c6c2..80fb9cbedb 100644
--- a/spec/appendices.md
+++ b/spec/appendices.md
@@ -52,24 +52,27 @@ Addison Phillips,
Eemeli Aro,
Romulo Cintra,
Stanisław Małolepszy,
+Tim Chevalier,
Elango Cheran,
Richard Gibson,
-Tim Chevalier,
Mihai Niță,
-Shane F. Carr,
Mark Davis,
Steven R. Loomis,
+Shane F. Carr,
+Matt Radbourne,
Caleb Maclennan,
David Filip,
Daniel Minor,
-Christopher Dieringer,
+Christopher Dieringer,
+Bruno Haible,
+Danny Gleckler,
George Rhoten,
Ujjwal Sharma,
Daniel Ehrenberg,
Markus Scherer,
Zibi Braniecki,
-Matt Radbourne,
-Bruno Haible,
+Lionel Rowe,
+Luca Casonato,
and Rafael Xavier de Souza.
Addison Phillips was chair of the working group from January 2023.
diff --git a/spec/formatting.md b/spec/formatting.md
index cf33d56229..78a2a71347 100644
--- a/spec/formatting.md
+++ b/spec/formatting.md
@@ -2,8 +2,8 @@
## Introduction
-This document defines the behaviour of a MessageFormat 2.0 implementation
-when formatting a message for display in a user interface, or for some later processing.
+This section defines the behavior of a MessageFormat 2.0 implementation
+when formatting a _message_ for display in a user interface, or for some later processing.
To start, we presume that a _message_ has either been parsed from its syntax
or created from a data model description.
@@ -80,12 +80,12 @@ nor be made available to _function handlers_.
## Formatting Context
-A message's **_formatting context_** represents the data and procedures that are required
-for the message's _expression resolution_, _pattern selection_ and _formatting_.
+A _message_'s **_formatting context_** represents the data and procedures that are required
+for the _message_'s _expression resolution_, _pattern selection_ and _formatting_.
At a minimum, it includes:
-- Information on the current **_locale_**,
+- Information on the current **_[locale](https://www.w3.org/TR/i18n-glossary/#dfn-locale)_**,
potentially including a fallback chain of locales.
This will be passed on to formatting functions.
@@ -98,9 +98,9 @@ At a minimum, it includes:
This is often determined by a user-provided argument of a formatting function call.
- The _function registry_,
- providing the _function handlers_ of the functions referred to by message _functions_.
+ providing the _function handlers_ of the functions referred to by _message_ _functions_.
-- Optionally, a fallback string to use for the message if it is not _valid_.
+- Optionally, a fallback string to use for the _message_ if it is not _valid_.
Implementations MAY include additional fields in their _formatting context_.
diff --git a/spec/u-namespace.md b/spec/u-namespace.md
index 03a7134313..88519d45ad 100644
--- a/spec/u-namespace.md
+++ b/spec/u-namespace.md
@@ -8,7 +8,7 @@ rather than function-specific.
It might also be used to define _functions_ in a future release.
The CLDR Technical Committee of the Unicode Consortium
-manages the specification for this namespace, hence the name `u:`.
+manages the specification for this namespace, hence the _namespace_ `u:`.
## Options
@@ -38,10 +38,10 @@ well-formed [BCP 47](https://www.rfc-editor.org/rfc/bcp/bcp47.txt)
language tags,
or an implementation-defined list of such tags.
-If this option is set on _markup_, a _Bad Option_ error is emitted
-and the value of the `u:locale` option is ignored.
+If this _option_ is set on _markup_, a _Bad Option_ error is emitted
+and the value of the `u:locale` _option_ is ignored.
-During processing, the `u:locale` option
+During processing, the `u:locale` _option_
MUST be removed from the resolved mapping of _options_
before calling the _function handler_.