Editorial: more nits and more <div algorithm> wrappers

Related to #1526.

Author: dlrobertson

fetch.bs

@@ -2666,6 +2666,7 @@ functionality.
 
 <h3 id=resolving-domains>Resolving domains</h3>
 
+<div algorithm>
 <p tracking-vector>To
 <dfn export id=resolve-an-origin oldids=resolve-a-domain>resolve an origin</dfn>, given a
 <a for=/>network partition key</a> <var>key</var> and an <a for=/>origin</a> <var>origin</var>:
@@ -2710,6 +2711,7 @@ be used as part of the cache key.
  system the Fetch Standard establishes. Other documents ought not to build on this primitive without
  having a considered discussion with the Fetch Standard community first.
 </div>
+</div>
 
 
 <h3 id=connections>Connections</h3>
@@ -2742,6 +2744,7 @@ information pertaining to the process of obtaining a connection. It has the foll
  <dd>A <a for=/>byte sequence</a>.
 </dl>
 
+<div algorithm>
 <p>To <dfn>clamp and coarsen connection timing info</dfn>, given a
 <a for=/>connection timing info</a> <var>timingInfo</var>, a {{DOMHighResTimeStamp}}
 <var>defaultStartTime</var>, and a boolean <var>crossOriginIsolatedCapability</var>, run these
@@ -2778,12 +2781,14 @@ steps:
  <a for="connection timing info">ALPN negotiated protocol</a> is <var>timingInfo</var>'s
  <a for="connection timing info">ALPN negotiated protocol</a>.
 </ol>
+</div>
 
 <hr>
 
 <p>A <dfn>new connection setting</dfn> is "<code>no</code>", "<code>yes</code>", or
 "<code>yes-and-dedicated</code>".
 
+<div algorithm="obtain a connection">
 <p>To <dfn export id=concept-connection-obtain>obtain a connection</dfn>, given a
 <a>network partition key</a> <var>key</var>, <a for=/>URL</a> <var>url</var>, boolean
 <var>credentials</var>, an optional <a>new connection setting</a> <var>new</var> (default
@@ -2828,7 +2833,8 @@ steps:
    <li><p>Set <var>timingInfo</var>'s <a for="connection timing info">domain lookup start time</a>
    to the <a for=/>unsafe shared current time</a>.
 
-   <li><p>Let <var>hosts</var> be « <var>origin</var>'s <a for=origin>host</a> ».
+   <li><p>Let <var>hosts</var> be « <var>url</var>'s <a for=url>origin</a>'s
+   <a for=origin>host</a> ».
 
    <li><p>If <var>proxy</var> is "<code>DIRECT</code>", then set <var>hosts</var> to the result of
    running <a>resolve an origin</a> given <var>key</var> and <var>url</var>'s <a for=url>origin</a>.
@@ -2869,9 +2875,11 @@ management that are best left to the discretion of implementers. Describing this
 keyed on <a for=/>credentials</a>. The latter clarifies that, e.g., TLS session identifiers are not
 reused across <a>connections</a> whose <a for=connection>credentials</a> are false with
 <a>connections</a> whose <a for=connection>credentials</a> are true.
+</div>
 
 <hr>
 
+<div algorithm>
 <p>To <dfn>create a connection</dfn>, given a <a for=/>network partition key</a> <var>key</var>,
 <a for=/>origin</a> <var>origin</var>, boolean <var>credentials</var>, string <var>proxy</var>,
 <a for=/>host</a> <var>host</var>, <a for=/>connection timing info</a> <var>timingInfo</var>, and
@@ -2925,9 +2933,11 @@ boolean <var>http3Only</var>, run these steps:
 
  <li><p>Return <var>connection</var>.
 </ol>
+</div>
 
 <hr>
 
+<div algorithm>
 <p>To <dfn>record connection timing info</dfn> given a <a for=/>connection</a>
 <var>connection</var>, let <var>timingInfo</var> be <var>connection</var>'s
 <a for=connection>timing info</a> and observe these requirements:
@@ -2977,6 +2987,7 @@ boolean <var>http3Only</var>, run these steps:
 
 <p class=note>The <a for=/>clamp and coarsen connection timing info</a> algorithm ensures that
 details of reused connections are not exposed and time values are coarsened.
+</div>
 
 
 <h3 id=network-partition-keys>Network partition keys</h3>