Avoid breaking up algorithm steps with NOTE

Author: catamorphism

spec/formatting.md

@@ -936,18 +936,8 @@ The _Default Bidi Strategy_ is defined as follows:
    right-to-left directionality, and to the message's directionality not being known.
 1. For each _expression_ `exp` in _pattern_:
    1. Let `fmt` be the formatted string representation of the _resolved value_ of `exp`.
-   1. Let `dir` be the directionality of the _resolved value_ of `exp`,
+   1. Let `dir` be `DIR(exp)`,
       one of « `'LTR'`, `'RTL'`, `'unknown'` », with the same meanings as for `msgdir`.
-      > [!NOTE]
-      > _Resolved values_ need to track two different pieces of metadata about directionality:
-      > the "isolate" flag (see the next step for how that is used), which determines
-      > whether the formatted result needs to be isolated; and the directionality itself.
-      > Each _function handler_ can have its own means for determining the directionality
-      > of the _resolved value_ it returns.
-      > Alternately, an implementation could elide this tracking and instead determine
-      > the directionality from the locale.
-      > The directionality SHOULD NOT be determined by introspecting
-      > the character sequence in `fmt`.
    1. Let the boolean value `isolate` be
       True if the `u:dir` _option_ of the _resolved value_ of `exp` has a value other than `'inherit'`,
       or False otherwise.
@@ -967,4 +957,20 @@ The _Default Bidi Strategy_ is defined as follows:
          prefix `fmt` with U+2068 FIRST STRONG ISOLATE
          and postfix it with U+2069 POP DIRECTIONAL ISOLATE.
 
+The auxiliary function `DIR`, which maps an _expression_ to one of
+« `'LTR'`, `'RTL'`, `'unknown'` », is expected to be defined using the
+_resolved value_ of the _expression_. An implementation can use
+a representation of _resolved values_ that tracks two different
+pieces of metadata about directionality: the `isolate` flag used in step 2(iii),
+and the directionality itself. Each _function handler_ can have its own means
+for determining the directionality annotation on the _resolved value_ it returns.
+Alternately, an implementation could simply compute `DIR(exp)` based on the
+locale.
+
+> [!NOTE]
+> `DIR(exp)` SHOULD NOT be determined by introspecting
+> the character sequence in the formatted string representation
+> of the resolved value of `exp`.
+
+