Revert a change to a date

index.html

@@ -1927,10 +1927,10 @@ <h3 class="heading settled" data-level="4.2" id="certificates"><span class="secn
       <td>One of the values listed above.
      <tr>
       <td>Issuer Name
-      <td>CN = The <code>model-name</code> from the <code>agent-info</code> message.<br> O = See note.<br> L = See note.<br> ST = See note.<br> C = See note.<br> 
+      <td>CN = The <code>model-name</code> from the <code>agent-info</code> message.<br> O = See note.<br> L = See note.<br> ST = See note.<br> C = See note.<br>
      <tr>
       <td>Subject Name
-      <td>CN = <code>&lt;fp></code>._openscreen._udp.local<br> O = See note.<br> 
+      <td>CN = <code>&lt;fp></code>._openscreen._udp.local<br> O = See note.<br>
      <tr>
       <td>Subject Public Key Algorithm
       <td>Elliptic Curve Public Key
@@ -2877,7 +2877,7 @@ <h2 class="heading settled" data-level="9" id="streaming-protocol"><span class="
    <h3 class="heading settled" data-level="9.1" id="streaming-protocol-capabilities"><span class="secno">9.1. </span><span class="content">Streaming Protocol Capabilities</span><a class="self-link" href="#streaming-protocol-capabilities"></a></h3>
     If the advertiser is already authenticated, the requester has the ability to
 request additional information by sending an <a data-link-type="dfn" href="#streaming-capabilities-request" id="ref-for-streaming-capabilities-request">streaming-capabilities-request</a> message, and receive back a <a data-link-type="dfn" href="#streaming-capabilities-response" id="ref-for-streaming-capabilities-response">streaming-capabilities-response</a> message with the
-following fields: 
+following fields:
    <dl>
     <dt data-md>receive-audio (required)
     <dd data-md>
@@ -3741,7 +3741,7 @@ <h4 class="heading settled" data-level="12.6.1" id="instance-names"><span class=
 before being shown in full as a <a data-link-type="dfn" href="#verified-display-name" id="ref-for-verified-display-name">verified display name</a>.</p>
    <div class="note" role="note">
      This means there are three categories of display names that agents should be
-capable of handling: 
+capable of handling:
     <ol>
      <li>Truncated and unverified DNS-SD Instance Names, which should not be shown to the user.
      <li>Complete but unverified DNS-SD Instance Names, which can be shown as
@@ -5013,7 +5013,7 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
    <dt id="biblio-rfc8466">[RFC8466]
    <dd>B. Wen; et al. <a href="https://tools.ietf.org/html/rfc8466">A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery</a>. October 2018. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc8466">https://tools.ietf.org/html/rfc8466</a>
    <dt id="biblio-security-privacy-questionnaire">[SECURITY-PRIVACY-QUESTIONNAIRE]
-   <dd>Lukasz Olejnik; Jason Novak. <a href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>. 10 September 2019. NOTE. URL: <a href="https://www.w3.org/TR/security-privacy-questionnaire/">https://www.w3.org/TR/security-privacy-questionnaire/</a>
+   <dd>Lukasz Olejnik; Jason Novak. <a href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>. 23 May 2019. NOTE. URL: <a href="https://www.w3.org/TR/security-privacy-questionnaire/">https://www.w3.org/TR/security-privacy-questionnaire/</a>
   </dl>
   <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content">Issues Index</span><a class="self-link" href="#issues-index"></a></h2>
   <div style="counter-reset:issue">