diff --git a/docs/outstanding.md b/docs/outstanding.md
index b116356..0987d27 100644
--- a/docs/outstanding.md
+++ b/docs/outstanding.md
@@ -236,7 +236,9 @@ observes that publishing on Play is what turns SAF from a preference into a cons
 distribution.md §6 argues the coupling runs the other way for this project — F-Droid asks nothing
 that ARCH §6.9 does not already require. Spike S11, the Play permissions dry-run, has not run, and
 until it does that argument is reasoned rather than confirmed. Two of the five channels also exist
-as decisions rather than as recipes, and no Flatpak has been built here at all. Related, NFR-COMPAT-1's baseline is real but scattered — API 28/36 live in the Android
+as decisions rather than as recipes, and no Flatpak has been built here at all.
+
+Related, NFR-COMPAT-1's baseline is real but scattered — API 28/36 live in the Android
 Dockerfile and are checked in CI against the built ELF, which is good — while the items the
 requirement singles out are missing: whether `shaderFloat16` and 16-bit storage are required (the
 one it flags as jeopardising R1), minimum RAM, minimum desktop Mesa, and a named reference device
diff --git a/docs/requirements.md b/docs/requirements.md
index a22bd10..b238dc1 100644
--- a/docs/requirements.md
+++ b/docs/requirements.md
@@ -74,8 +74,8 @@ results.
 
 **On R5's tiling.** An earlier draft added two clauses to R5's criterion: *"only visible tiles are
 computed; panning recomputes only newly exposed tiles"*. They have been struck, and the reason is
-the same one that FR-DSP-2 was rewritten for rather than implemented — [frame-budget.md](frame-budget.md)
-measured it.
+the same one FR-DSP-2 was rewritten for rather than implemented:
+[frame-budget.md](frame-budget.md) measured it.
 
 R5's actual demand is met and tested. The display pipeline works at viewport resolution:
 `Framing::view` shrinks the sampled region while the render target keeps its size, so zooming raises
@@ -547,9 +547,10 @@ and bit depth are configurable.
 
 **AVIF and JPEG XL are post-v1** and are not part of this requirement's acceptance. Either may still
 be listed in the settings page before its encoder exists, on one condition: choosing it shall fail
-with a typed error naming the format, never with a file. `every_offered_format_either_encodes_or_explains_itself`
-walks every format the page offers and enforces exactly that, so a format cannot be added to the
-picker and quietly reach an encoder that does not handle it.
+with a typed error naming the format, never with a file. The test
+`every_offered_format_either_encodes_or_explains_itself` walks every format the page offers and
+enforces exactly that, so a format cannot be added to the picker and quietly reach an encoder that
+does not handle it.
 
 *On splitting this requirement.* It read as one undifferentiated list — "JPEG, PNG, TIFF (8 and
 16-bit), and AVIF or JPEG XL" — which left it neither met nor unmet. Three formats, both TIFF