Fix HTML structure (#101)

* Move paragraphs to valid places in the HTML structure.

* Fix nested ordered list.

index.html

@@ -1055,13 +1055,6 @@ <h2>Dereferencing the Primary Resource</h2>
 					<li>Return the <var>output <a>service endpoint</a> URL</var>.</li>
 				</ol>
 				</li>
-
-				<p class="issue" data-number="85">There have been discussions whether in addition to the DID parameter <code>service</code>,
-					there could also be a DID parameter <code>serviceType</code> to select services based
-					on their type rather than ID.
-					See <a href="https://lists.w3.org/Archives/Public/public-credentials/2019Jun/0028.html">
-					comments by Dave Longley</a> about `serviceType`.</p>
-
 				<li>Otherwise, if the <var>input <a>DID URL</a></var> contains no <a>DID path</a> and no <a>DID query</a>:
 				<pre class="example nohighlight">did:example:1234</pre>
 				<ol class="algorithm">
@@ -1087,6 +1080,12 @@ <h2>Dereferencing the Primary Resource</h2>
 				</li>
 			</ol>
 
+			<p class="issue" data-number="85">There have been discussions whether in addition to the DID parameter <code>service</code>,
+				there could also be a DID parameter <code>serviceType</code> to select services based
+				on their type rather than ID.
+				See <a href="https://lists.w3.org/Archives/Public/public-credentials/2019Jun/0028.html">
+					comments by Dave Longley</a> about `serviceType`.</p>
+
 		</section>
 
 		<section id="dereferencing-algorithm-secondary">
@@ -1106,25 +1105,27 @@ <h2>Dereferencing the Secondary Resource</h2>
 					the <var>output <a>service endpoint</a> URL</var> "inherits" the <a>DID fragment</a> of the
 					<var>input <a>DID URL</a></var>.</li>
 					<li>Return the <var>output <a>service endpoint</a> URL</var>.</li>
-					<p class="note">
-					This behavior of the <a>DID fragment</a> is analogous to the handling of a fragment in an HTTP URL in the
-					case when dereferencing it returns an HTTP <code>3xx</code> (Redirection) response with a
-					<code>Location</code> header (see section 7.1.2 of [[RFC7231]].
-					</p>
 				</ol>
 				<li>Otherwise, dereference the secondary resource identified by the DID fragment as defined by the media type ([[RFC2046]]) of the primary resource.
 				For example, if the primary resource is a representation of a DID document with media type <code>application/did+ld+json</code>, then
 				the fragment is treated according to the rules associated with the
 				<a href="https://www.w3.org/TR/json-ld11/#iana-considerations">JSON-LD 1.1: application/ld+json media type</a>
 				[JSON-LD11].
 			</li>
-				<p class="note">
-					This use of the <a>DID fragment</a> is consistent with the definition of the fragment identifier in
-					[[RFC3986]]. It identifies a <em>secondary resource</em> which is a subset of the <em>primary resource</em>
-					(the <a>DID document</a>).
-				</p>
 			</ol>
 
+			<p class="note">
+				This use of the <a>DID fragment</a> is consistent with the definition of the fragment identifier in
+				[[RFC3986]]. It identifies a <em>secondary resource</em> which is a subset of the <em>primary resource</em>
+				(the <a>DID document</a>).
+			</p>
+
+			<p class="note">
+				This behavior of the <a>DID fragment</a> is analogous to the handling of a fragment in an HTTP URL in the
+				case when dereferencing it returns an HTTP <code>3xx</code> (Redirection) response with a
+				<code>Location</code> header (see section 7.1.2 of [[RFC7231]].
+			</p>
+
 		</section>
 
 	</section>
@@ -1841,7 +1842,7 @@ <h2>HTTP(S) Binding</h2>
 		<a href="#resolving"></a>) and/or <a>DID URL dereferencing</a> function (see <a href="#dereferencing"></a>)
 		can be executed as follows:</p>
 		<ol class="algorithm">
-			<li>Initialize a <var>request HTTP(S) URL</var> with the <var><a>DID resolver</a> HTTP(S) endpoint</var>.</li>
+			<li>Initialize a <var>request HTTP(S) URL</var> with the <var><a>DID resolver</a> HTTP(S) endpoint</var>.
 			<ol class="algorithm">
 				<li>Append the <var>input <a>DID</a></var> or
 				<var>input <a>DID URL</a></var> to the <var>request HTTP(S) URL</var>. Certain characters
@@ -1852,6 +1853,7 @@ <h2>HTTP(S) Binding</h2>
 				<li>Encode all other resolution options as
 				query parameters in the <var>request HTTP(S) URL</var>.</li>
 			</ol>
+			</li>
 			<li>Execute an HTTP <code>GET</code> request on the <var>request HTTP(S) URL</var>.</li>
 			<li>Dereference the <var>input <a>DID</a></var> or <var>input <a>DID URL</a></var> by executing the
 				<a>DID URL dereferencing</a> algorithm as defined in <a href="#dereferencing"></a></li>