From 8d8160394073dac4ddf2550aebf90a9ce2043110 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marcos=20C=C3=A1ceres?= <marcos@marcosc.com>
Date: Wed, 6 Oct 2021 13:20:21 +1100
Subject: [PATCH] Editorial: clean up

---
 index.html | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/index.html b/index.html
index a15b8d821..616b4e81b 100644
--- a/index.html
+++ b/index.html
@@ -819,11 +819,10 @@ <h3>
           `id` member
         </h3>
         <p>
-          The [=manifest's=] <code><dfn data-export="" data-dfn-for="manifest"
-          id="identity">id</dfn></code> member is a <a>string</a> that
-          represents the <dfn>identity</dfn> for the application. The
-          [=identity=] takes the form of a URL, which is same origin as the
-          start URL.
+          The [=manifest's=] <code><dfn data-export="" data-dfn-for=
+          "manifest">id</dfn></code> member is a <a>string</a> that represents
+          the <dfn>identity</dfn> for the application. The [=identity=] takes
+          the form of a URL, which is same origin as the start URL.
         </p>
         <p>
           The [=identity=] is used by user agents to uniquely identify the
@@ -871,10 +870,10 @@ <h3>
           <li>Set |manifest|["id"] to |id|.
           </li>
         </ol>
-        <aside class="example">
+        <aside class="example" title="Resulting ids">
           <p>
-            Below table shows some example cases of the |identity| processing
-            algorithm.
+            Below table shows some example `id`s resulting from the [=process
+            the `id` member=] steps.
           </p>
           <table class="data">
             <tr>