From 8f4a021d6e81adf7b43f493e231a3e009a973b9e Mon Sep 17 00:00:00 2001
From: Barry Pollard <barrypollard@google.com>
Date: Thu, 5 Mar 2026 17:30:19 +0000
Subject: [PATCH 1/2] Clean up script-initiated patching example

---
 patching-explainer.md | 35 +++++++++--------------------------
 1 file changed, 9 insertions(+), 26 deletions(-)

diff --git a/patching-explainer.md b/patching-explainer.md
index 8d61566..66a92f6 100644
--- a/patching-explainer.md
+++ b/patching-explainer.md
@@ -18,7 +18,7 @@ This proposal introduces partial out-of-order HTML streaming as part of the web
 
 Patches are delivered using a `<template>` element with the `for` attribute and target an existing elements in the DOM. These patches require no scripts to apply (are declarative) and can appear in the main response HTML to support out-of-order streaming.
 
-Patches can be be applied later in the page lifecycle using JavaScript, see [interaction with script-initiated patching](#interaction-with-script-initiated-patching).
+Patches can be be applied later in the page lifecycle using JavaScript, see [script-initiated patching](#script-initiated-patching).
 
 ### Proposed markup
 
@@ -84,24 +84,6 @@ To support multiple ranges, processing instructions can be named. Any number of
 </template>
 ```
 
-Multiple `<?marker>` elements without place-holder content is also supported in a similar manner:
-
-```html
-<div marker="results">
- <?marker name="part-one">
- <hr>
- <?marker name="part-two">
-</div>
-
-<template for="results#part-one">
-  <p>Actual 1st part of the content</p>
-</template>
-
-<template for="results#part-two">
-  <p>Actual 2nd part of the content</p>
-</template>
-```
-
 A few details about patching:
 
 - Templates with a valid `for` attribute are not attached to the DOM, while templates that don't apply are attached to signal an error.
@@ -162,9 +144,10 @@ For example:
 ```html
 <!-- load the document shell -->
 <div id=container>
-  <div marker="results more">
-    <?start name=results>
+  <div marker="results">
+    <?start name="next-result">
     Loading...
+    <?end>
   </div>
 </div>
 <!-- later, as a response to navigation or a click or anything... -->
@@ -172,18 +155,18 @@ For example:
   async function update_results() {
   const writer = container.streamAppendHTMLUnsafe().getWriter();
    await writer.write(`
-      <template for=result>
-        <?start name=results>
+      <template for=results#next-result>
         Result 1
-        <?marker name=more>
+        <?marker name="next-result">
       </template>
     `);
    await writer.write(`
-      <template for=more>
+      <template for=results#next-result>
         Result 2
-        <?marker name=more>
+        <?marker name="next-result">
       </template>
     `);
+   // Add as many more results streaming in later as you see fit.
   }
 </script>
 ```

From 816b6bf776a9103074404d28f9c81509fd2e1167 Mon Sep 17 00:00:00 2001
From: Barry Pollard <barrypollard@google.com>
Date: Thu, 5 Mar 2026 17:32:21 +0000
Subject: [PATCH 2/2] Merge main

---
 patching-explainer.md | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/patching-explainer.md b/patching-explainer.md
index 66a92f6..4153061 100644
--- a/patching-explainer.md
+++ b/patching-explainer.md
@@ -18,7 +18,7 @@ This proposal introduces partial out-of-order HTML streaming as part of the web
 
 Patches are delivered using a `<template>` element with the `for` attribute and target an existing elements in the DOM. These patches require no scripts to apply (are declarative) and can appear in the main response HTML to support out-of-order streaming.
 
-Patches can be be applied later in the page lifecycle using JavaScript, see [script-initiated patching](#script-initiated-patching).
+Patches can be be applied later in the page lifecycle using JavaScript, see [interaction with script-initiated patching](#interaction-with-script-initiated-patching).
 
 ### Proposed markup
 
@@ -84,6 +84,24 @@ To support multiple ranges, processing instructions can be named. Any number of
 </template>
 ```
 
+Multiple `<?marker>` elements without place-holder content is also supported in a similar manner:
+
+```html
+<div marker="results">
+ <?marker name="part-one">
+ <hr>
+ <?marker name="part-two">
+</div>
+
+<template for="results#part-one">
+  <p>Actual 1st part of the content</p>
+</template>
+
+<template for="results#part-two">
+  <p>Actual 2nd part of the content</p>
+</template>
+```
+
 A few details about patching:
 
 - Templates with a valid `for` attribute are not attached to the DOM, while templates that don't apply are attached to signal an error.