Final preparations for v47 pourover (#1021)

* Final preparations for v47 pourover

This PR incorporates additional fixes to #1001 found when assembling the "pour over" version of the specification for v47.

* Update number.md

* Update datetime.md

Fix nesting level.
Fix broken note.

* Link to default-function head

* syntax.md: save some steps on link fixing

Author: aphillips

spec/functions/datetime.md

@@ -1,4 +1,4 @@
-## Date and Time Value Formatting
+### Date and Time Value Formatting
 
 This subsection describes the _functions_ and _options_ for date/time formatting.
 
@@ -12,7 +12,7 @@ This subsection describes the _functions_ and _options_ for date/time formatting
 > The types of queries found in implementations such as `java.time.TemporalAccessor`
 > are complex and user expectations might be inconsistent with good I18N practices.
 
-### The `:datetime` function
+#### The `:datetime` function
 
 The function `:datetime` is used to format date/time values, including
 the ability to compose user-specified combinations of fields.
@@ -26,14 +26,14 @@ If no options are specified, this function defaults to the following:
 > in JavaScript and with `{d,date}` in ICU MessageFormat 1.0.
 > This is because, unlike those implementations, `:datetime` is distinct from `:date` and `:time`.
 
-#### Operands
+##### Operands
 
 The _operand_ of the `:datetime` function is either
 an implementation-defined date/time type
 or a _date/time literal value_, as defined in [Date and Time Operand](#date-and-time-operands).
 All other _operand_ values produce a _Bad Operand_ error.
 
-#### Options
+##### Options
 
 The `:datetime` function can use either the appropriate _style options_
 or can use a collection of _field options_ (but not both) to control the formatted
@@ -54,7 +54,7 @@ with _options_ on the _expression_ taking priority over any option values of the
 > [options](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/resolvedOptions#description)
 > in JavaScript's `Intl.DateTimeFormat`.
 
-##### Style Options
+###### Style Options
 
 The function `:datetime` has these _style options_.
 
@@ -69,12 +69,13 @@ The function `:datetime` has these _style options_.
   - `medium`
   - `short`
 
-##### Field Options
+###### Field Options
 
 _Field options_ describe which fields to include in the formatted output
 and what format to use for that field.
 
-> [!NOTE] > _Field options_ do not have default values because they are only to be used
+> [!NOTE]
+> _Field options_ do not have default values because they are only to be used
 > to compose the formatter.
 
 The function `:datetime` has the following _field options_:
@@ -120,29 +121,29 @@ The function `:datetime` has the following _field options_:
   - `shortGeneric`
   - `longGeneric`
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:datetime` _function_
 contains an implementation-defined date/time value
 of the _operand_ of the annotated _expression_,
 together with the resolved options values.
 
-### The `:date` function
+#### The `:date` function
 
 The function `:date` is used to format the date portion of date/time values.
 
 If no options are specified, this function defaults to the following:
 
 - `{$d :date}` is the same as `{$d :date style=medium}`
 
-#### Operands
+##### Operands
 
 The _operand_ of the `:date` function is either
 an implementation-defined date/time type
 or a _date/time literal value_, as defined in [Date and Time Operand](#date-and-time-operands).
 All other _operand_ values produce a _Bad Operand_ error.
 
-#### Options
+##### Options
 
 The function `:date` has these _options_:
 
@@ -158,7 +159,7 @@ it can include other option values.
 Any _operand_ option values matching the `:datetime` _style options_ or _field options_ are ignored,
 as is any `style` option.
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:date` _function_
 is implementation-defined.
@@ -167,22 +168,22 @@ An implementation MAY emit a _Bad Operand_ or _Bad Option_ error (as appropriate
 when a _variable_ annotated directly or indirectly by a `:date` _annotation_
 is used as an _operand_ or an _option_ value.
 
-### The `:time` function
+#### The `:time` function
 
 The function `:time` is used to format the time portion of date/time values.
 
 If no options are specified, this function defaults to the following:
 
 - `{$t :time}` is the same as `{$t :time style=short}`
 
-#### Operands
+##### Operands
 
 The _operand_ of the `:time` function is either
 an implementation-defined date/time type
 or a _date/time literal value_, as defined in [Date and Time Operand](#date-and-time-operands).
 All other _operand_ values produce a _Bad Operand_ error.
 
-#### Options
+##### Options
 
 The function `:time` has these _options_:
 
@@ -198,7 +199,7 @@ it can include other option values.
 Any _operand_ option values matching the `:datetime` _style options_ or _field options_ are ignored,
 as is any `style` option.
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:time` _function_
 is implementation-defined.
@@ -207,7 +208,7 @@ An implementation MAY emit a _Bad Operand_ or _Bad Option_ error (as appropriate
 when a _variable_ annotated directly or indirectly by a `:time` _annotation_
 is used as an _operand_ or an _option_ value.
 
-### Date and Time Operands
+#### Date and Time Operands
 
 The _operand_ of a date/time function is either
 an implementation-defined date/time type
@@ -257,7 +258,7 @@ For more information, see [Working with Timezones](https://w3c.github.io/timezon
 > Support for these extensions is expected to be required in the post-tech preview.
 > See: https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/
 
-### Date and Time Override Options
+#### Date and Time Override Options
 
 **_<dfn>Date/time override options</dfn>_** are _options_ that allow an _expression_ to
 override values set by the current locale,

spec/functions/number.md

@@ -1,14 +1,14 @@
-## Numeric Value Selection and Formatting
+### Numeric Value Selection and Formatting
 
-### The `:number` function
+#### The `:number` function
 
 The function `:number` is a selector and formatter for numeric values.
 
-#### Operands
+##### Operands
 
 The function `:number` requires a [Number Operand](#number-operands) as its _operand_.
 
-#### Options
+##### Options
 
 Some options do not have default values defined in this specification.
 The defaults for these options are implementation-dependent.
@@ -83,27 +83,27 @@ with _options_ on the _expression_ taking priority over any option values of the
 > would be formatted with the resolved options
 > `{ minimumFractionDigits: '1', signDisplay: 'always' }`.
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:number` _function_
 contains an implementation-defined numerical value
 of the _operand_ of the annotated _expression_,
 together with the resolved options' values.
 
-#### Selection
+##### Selection
 
 The _function_ `:number` performs selection as described in [Number Selection](#number-selection) below.
 
-### The `:integer` function
+#### The `:integer` function
 
 The function `:integer` is a selector and formatter for matching or formatting numeric
 values as integers.
 
-#### Operands
+##### Operands
 
 The function `:integer` requires a [Number Operand](#number-operands) as its _operand_.
 
-#### Options
+##### Options
 
 Some options do not have default values defined in this specification.
 The defaults for these options are implementation-dependent.
@@ -148,18 +148,18 @@ Option values with the following names are however discarded if included in the
 - `maximumFractionDigits`
 - `minimumSignificantDigits`
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with an `:integer` _function_
 contains the implementation-defined integer value
 of the _operand_ of the annotated _expression_,
 together with the resolved options' values.
 
-#### Selection
+##### Selection
 
 The _function_ `:integer` performs selection as described in [Number Selection](#number-selection) below.
 
-### The `:math` function
+#### The `:math` function
 
 > [!IMPORTANT]
 > The _function_ `:math` has a status of **Draft**.
@@ -182,11 +182,11 @@ numeric values to which a mathematical operation has been applied.
 > * *   {{{$name} and {$others_count} other users liked your post.}}
 > ```
 
-#### Operands
+##### Operands
 
 The function `:math` requires a [Number Operand](#number-operands) as its _operand_.
 
-#### Options
+##### Options
 
 The options on `:math` are exclusive with each other,
 and exactly one option is always required.
@@ -204,7 +204,7 @@ or if an _option_ value is not a [digit size option](#digit-size-options),
 a _Bad Option_ error is emitted
 and a _fallback value_ used as the _resolved value_ of the _expression_.
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:math` _function_
 contains the implementation-defined numeric value
@@ -231,11 +231,11 @@ The `:math` _options_ are not included in the resolved option values.
 > In such cases, implementations can emit an _Unsupported Operation_ error
 > or they might just silently overflow the underlying data value.
 
-#### Selection
+##### Selection
 
 The _function_ `:math` performs selection as described in [Number Selection](#number-selection) below.
 
-### The `:currency` function
+#### The `:currency` function
 
 > [!IMPORTANT]
 > The _function_ `:currency` has a status of **Draft**.
@@ -244,7 +244,7 @@ The _function_ `:math` performs selection as described in [Number Selection](#nu
 The _function_ `:currency` is a _formatter_ for currency values,
 which are a specialized form of numeric formatting.
 
-#### Operands
+##### Operands
 
 The _operand_ of the `:currency` function can be one of any number of
 implementation-defined types,
@@ -294,7 +294,7 @@ A [Number Operand](#number-operands) without a `currency` _option_ results in a
 > }
 > ```
 
-#### Options
+##### Options
 
 Some options do not have default values defined in this specification.
 The defaults for these options are implementation-dependent.
@@ -406,14 +406,14 @@ with _options_ on the _expression_ taking priority over any option values of the
 > would be formatted with the resolved options
 > `{ currencySign: 'accounting', trailingZeroDisplay: 'stripIfInteger', currency: 'USD' }`.
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:currency` _function_
 contains an implementation-defined currency value
 of the _operand_ of the annotated _expression_,
 together with the resolved options' values.
 
-### The `:unit` function
+#### The `:unit` function
 
 > [!IMPORTANT]
 > The _function_ `:unit` has a status of **Draft**.
@@ -423,7 +423,7 @@ The _function_ `:unit` is proposed to be a RECOMMENDED formatter for unitized va
 that is, for numeric values associated with a unit of measurement.
 This is a specialized form of numeric formatting.
 
-#### Operands
+##### Operands
 
 The _operand_ of the `:unit` function can be one of any number of
 implementation-defined types,
@@ -457,7 +457,7 @@ A [Number Operand](#number-operands) without a `unit` _option_ results in a _Bad
 > }
 > ```
 
-#### Options
+##### Options
 
 Some _options_ do not have default values defined in this specification.
 The defaults for these _options_ are implementation-dependent.
@@ -532,14 +532,14 @@ with _options_ on the _expression_ taking priority over any _option_ values of t
 > would have the resolved options:
 > `{ unit: 'furlong', minimumFractionDigits: '2', minimumIntegerDigits: '1' }`.
 
-#### Resolved Value
+##### Resolved Value
 
 The _resolved value_ of an _expression_ with a `:unit` _function_
 consist of an implementation-defined unit value
 of the _operand_ of the annotated _expression_,
 together with the resolved _options_ and their resolved values.
 
-#### Unit Conversion
+##### Unit Conversion
 
 Implementations MAY support conversion to the locale's preferred units via the `usage` _option_.
 Implementing this _option_ is optional.
@@ -570,7 +570,7 @@ Implementations MUST NOT substitute the unit without performing the associated c
 >
 > This can produce "You have 405 feet to go."
 
-### Number Operands
+#### Number Operands
 
 The _operand_ of a number function is either an implementation-defined type or
 a literal whose contents match the following `number-literal` production.
@@ -608,7 +608,7 @@ number-literal = ["-"] (%x30 / (%x31-39 *DIGIT)) ["." 1*DIGIT] [%i"e" ["-" / "+"
 > or the type `com.ibm.icu.util.CurrencyAmount` can be used to set the currency and related
 > options (such as the number of fraction digits).
 
-### Digit Size Options
+#### Digit Size Options
 
 Some _options_ of number _functions_ are defined to take a "digit size option".
 The _function handlers_ for number _functions_ use these _options_ to control aspects of numeric display
@@ -632,7 +632,7 @@ If the value of a digit size option does not evaluate as a non-negative integer,
 or if the value exceeds any implementation-defined upper limit
 or any option-specific lower limit, a _Bad Option Error_ is emitted.
 
-### Number Selection
+#### Number Selection
 
 The value of the `select` _option_ MUST be set by a _literal_,
 as otherwise the _message_ might not be translatable.
@@ -674,7 +674,7 @@ numeric selectors perform as described below.
 > Implementations are not required to implement this exactly as written.
 > However, the observed behavior must be consistent with what is described here.
 
-#### Default Value of `select` Option
+##### Default Value of `select` Option
 
 The value `plural` is the default for the option `select`
 because it is the most common use case for numeric selection.
@@ -697,7 +697,7 @@ but can cause problems in target locales that the original developer is not cons
 > The `one` variant is needed by languages such as Polish or Russian.
 > Such locales typically also require other keywords such as `two`, `few`, and `many`.
 
-#### Rule Selection
+##### Rule Selection
 
 Rule selection is intended to support the grammatical matching needs of different
 languages/locales in order to support plural or ordinal numeric values.
@@ -757,7 +757,7 @@ for examples.
 > | 27 | `other` | 27 dní |
 > | 2.4 | `many` | 2,4 dne |
 
-#### Exact Literal Match Serialization
+##### Exact Literal Match Serialization
 
 If the numeric value of `resolvedSelector` is an integer
 and none of the following options are set for `resolvedSelector`,