Minor editorial fixes to Verifiable Timestamps section.

index.html

@@ -3408,23 +3408,23 @@ <h2>
 
     <section>
       <h2>
-Timestamps
+Verifiable Timestamps
       </h2>
 
       <p>
-<a>Verifiable timestamps</a> have significant utility for identifier
-records. This is a good fit for <a>DLTs</a>, since most offer some type of
-timestamp mechanism. Despite some transactional cost, they are the
-most censorship-resistant transaction ordering systems in the world,
-so they are nearly ideal for <a>DID document</a> timestamping. In some cases
-a <a>DLT</a>'s immediate timing is approximate, however their sense of
+<a>Verifiable timestamps</a> have significant utility for identifier records.
+This is a good fit for <a>DLTs</a>, since most offer some type of timestamp
+mechanism. Despite some transactional cost, they are the among the most
+censorship-resistant transaction ordering systems at the present, so they are
+nearly ideal for <a>DID document</a> timestamping. In some cases a <a>DLT</a>'s
+immediate timing is approximate, however their sense of
 <a href="https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki%23Abstract">
-"median time past" (see Bitcoin BIP 113)</a> can be precisely
-defined. A generic <a>DID document</a> timestamping mechanism could would
-work across all <a>DLTs</a> and might operate via a mechanism including
-either individual transactions or transaction batches. The generic
-mechanism was deemed out of scope for this version, although it may
-be included in a future version of this specification.
+"median time past" (see Bitcoin BIP 113)</a> can be precisely defined. A generic
+<a>DID document</a> timestamping mechanism could would work across all
+<a>DLTs</a> and might operate via a mechanism including either individual
+transactions or transaction batches. The generic mechanism was deemed out of
+scope for this version, although it may be included in a future version of this
+specification.
       </p>
     </section>
 

terms.html

@@ -258,16 +258,16 @@
 An identifier, as defined by [[RFC3986]].
   </dd>
 
-  <dt><dfn data-lt="verifiable timestamp">verifiable timestamp</dfn></dt>
+  <dt><dfn>verifiable timestamp</dfn></dt>
 
   <dd>
 A timestamp is verifiable if a third-party can confirm that a piece of data
-exists at a moment in time.  Verifying data integrity should be
-done in such a way that the party verifying the data can be certain that an
-authority or malicious party could not reasonably have modified the data as it
-existed at the attested moment.  If the data integrity could reasonably be
-modified or corrupted by a central authority or other party, the timestamp
-is not verifiable.
+existed at a specific moment in time. Verifying data integrity can be done in
+such a way that the party verifying the data is highly confident that an
+authority or malicious party could not have reasonably modified the data as it
+existed at the attested moment in time. If the data integrity could reasonably
+be modified or corrupted by a central authority or other party, the timestamp is
+not verifiable.
   </dd>
 
   <dt><dfn data-lt="">verification method</dfn></dt>