Editorial: add structure to create a connection

Use unordered list for substeps of the create a connection algorithm to improve readability.

Fixes #1571.

fetch.bs

@@ -2939,17 +2939,21 @@ boolean <var>http3Only</var>, run these steps:
   <a for=connection>credentials</a> is <var>credentials</var>, and <a for=connection>timing info</a>
   is <var>timingInfo</var>. <a for=/>Record connection timing info</a> given <var>connection</var>
   and use <var>connection</var> to establish an HTTP connection to <var>host</var>, taking
-  <var>proxy</var> and <var>origin</var> into account. [[!HTTP]] [[!HTTP1]] [[!TLS]]
+  <var>proxy</var> and <var>origin</var> into account, with the following caveats: [[!HTTP]]
+  [[!HTTP1]] [[!TLS]]
 
-  <p>If <var>http3Only</var> is true, then establish an HTTP/3 connection. [[!HTTP3]]
+  <ul>
+   <li><p>If <var>http3Only</var> is true, then establish an HTTP/3 connection. [[!HTTP3]]
 
-  <p>When establishing an HTTP/3 connection, include SETTINGS_ENABLE_WEBTRANSPORT with a value of 1
-  and H3_DATAGRAM with a value of 1 in the initial SETTINGS frame. [[!WEBTRANSPORT-HTTP3]]
-  [[!HTTP3-DATAGRAM]]
+   <li><p>When establishing an HTTP/3 connection, include SETTINGS_ENABLE_WEBTRANSPORT with a value
+   of 1 and H3_DATAGRAM with a value of 1 in the initial SETTINGS frame. [[!WEBTRANSPORT-HTTP3]]
+   [[!HTTP3-DATAGRAM]]
 
-  <p>If <var>credentials</var> is false, then do <em>not</em> send a TLS client certificate.
+   <li><p>If <var>credentials</var> is false, then do not send a TLS client certificate.
 
-  <p>If establishing a connection does not succeed (e.g., a TCP or TLS error), then return failure.
+   <li><p>If establishing a connection does not succeed (e.g., a TCP or TLS error), then return
+   failure.
+  </ul>
 
  <li>
   <p>Set <var>timingInfo</var>'s <a for="connection timing info">ALPN negotiated protocol</a> to