Script updating gh-pages from da30882. [ci skip]

add-0len-ext-to-report/draft-wang-ppm-dap-taskprov.html

@@ -1700,7 +1700,7 @@ <h2 id="name-security-considerations">
 and Aggregators have an inconsistent view of the the task configuration, then
 aggregation of reports will fail. This is guaranteed by the binding of the task
 ID (derived from the task configuration) to report shares provided by HPKE
-encryption. Furthermore, the presence of <code>task_prov</code> extension type in report
+encryption. Furthermore, the presence of <code>task_prov</code> extension type in the report
 share means Aggregators that do not recognize Taskprov extension must abort with
 <code>invalidMessage</code>, as described in (<span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-ppm-dap-07#section-4.4.3" class="relref">Section 4.4.3</a> of [<a href="#DAP" class="cite xref">DAP</a>]</span>). This prevents a
 malicious Leader from provisioning a modified task in Helper with other means,

add-0len-ext-to-report/draft-wang-ppm-dap-taskprov.txt

@@ -529,8 +529,8 @@ Table of Contents
    reports will fail.  This is guaranteed by the binding of the task ID
    (derived from the task configuration) to report shares provided by
    HPKE encryption.  Furthermore, the presence of task_prov extension
-   type in report share means Aggregators that do not recognize Taskprov
-   extension must abort with invalidMessage, as described in
+   type in the report share means Aggregators that do not recognize
+   Taskprov extension must abort with invalidMessage, as described in
    (Section 4.4.3 of [DAP]).  This prevents a malicious Leader from
    provisioning a modified task in Helper with other means, which can
    lead to compromised privacy guarantee in aggregation results.