Remove unnecessary whitespace.

Author: msporny

index.html

@@ -474,6 +474,7 @@ <h3>Ecosystem Overview</h3>
 Implementers are cautioned to remove this content if they desire to use the
 information as a valid document.
         </p>
+
       </section>
 
     </section>
@@ -2752,7 +2753,7 @@ <h3>Lifecycle Details</h3>
          src="diagrams/ecosystemdetail.svg" alt="diagram showing how
          credentials flow from issuer to holder, and optionally
          from one holder to another; and how
-         presentations flow from holder to verifier, 
+         presentations flow from holder to verifier,
          optionally from one verifier to another through verification and validation.
          All parties can use information from a logical
          verifiable data registry. Holder may also delete credential.">
@@ -3722,7 +3723,7 @@ <h3>Evidence</h3>
       "description": "This is a talk-aloud video of Alice demonstrating preparation of a double espresso drink.",
       <span class='comment'>// digest hash of the mp4 video file</span>
       "digestSRI": "sha384-zNNbQTWCSUSi0bbz7dbua...OHdzwELMYO9Mz68M26"
-    } 
+    }
   ]
 }
 </pre>
@@ -3909,10 +3910,10 @@ <h3>Reserved Extension Points</h3>
         <p>
 This specification reserves a number of [=properties=] to serve as possible
 extension points. While some implementers signaled interest in these properties,
-their inclusion in this specification was considered to be premature. Some of 
+their inclusion in this specification was considered to be premature. Some of
 these extension points were originally defined in previous versions of this
 specification, while others were not. It is important to note that none of these
-properties are defined by this specification. Consequently, implementers are 
+properties are defined by this specification. Consequently, implementers are
 cautioned that use of these properties is considered experimental.
         </p>
         <p>
@@ -4175,7 +4176,7 @@ <h3>Securing Mechanism Specifications</h3>
 other information that might be helpful (for example, during validation or for
 debugging purposes), such as securing mechanism data. A securing mechanism's
 verification algorithm MUST provide an interface that receives inputs of a media
-type ([=string=] |inputMediaType|) paired with either a sequence of bytes 
+type ([=string=] |inputMediaType|) paired with either a sequence of bytes
 ([=byte sequence=] |inputBytes|) or a document ([=map=] |inputDocument|), and
 returns a verification result with at least the following [=struct/items=]:
         </p>
@@ -4770,8 +4771,8 @@ <h3>Verification</h3>
 This section contains an algorithm that [=conforming verifier
 implementations=] MUST run when verifying a [=verifiable credential=] or a
 [=verifiable presentation=]. This algorithm takes inputs of a media
-type ([=string=] |inputMediaType|) paired with either a sequence of bytes 
-([=byte sequence=] |inputBytes|) or a document ([=map=] |inputDocument|), 
+type ([=string=] |inputMediaType|) paired with either a sequence of bytes
+([=byte sequence=] |inputBytes|) or a document ([=map=] |inputDocument|),
 and returns a [=map=] that contains the following:
         </p>