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

caw/roman-arch/draft-ietf-privacypass-architecture.html

@@ -2603,12 +2603,12 @@ <h3 id="name-partitioning-by-issuance-me">
 the tracked Client it would set the bit to <code>1</code>, and <code>0</code> otherwise. Adding
 additional bits provides an exponential increase in tracking granularity
 similarly to introducing more Issuers (though with more potential targeting).<a href="#section-6.1-1" class="pilcrow">¶</a></p>
-<p id="section-6.1-2">For this reason, deployments should take amount of metadata used by an Issuer
+<p id="section-6.1-2">For this reason, deployments should take the amount of metadata used by an Issuer
 in creating redemption tokens must into account -- together with the bits
 of information that Issuers may learn about Clients otherwise. Since this
 metadata may be useful for practical deployments of Privacy Pass, Issuers
 must balance this against the reduction in Client privacy.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
-<p id="section-6.1-3">The number of permitted metadata values often depends on deployment specific
+<p id="section-6.1-3">The number of permitted metadata values often depends on deployment-specific
 details. In general, limiting the amount of metadata permitted helps limit the
 extent to which metadata can uniquely identify individual Clients. Failure to
 bound the number of possible metadata values can therefore lead to reduction in

caw/roman-arch/draft-ietf-privacypass-architecture.txt

@@ -1137,14 +1137,14 @@ Table of Contents
    increase in tracking granularity similarly to introducing more
    Issuers (though with more potential targeting).
 
-   For this reason, deployments should take amount of metadata used by
-   an Issuer in creating redemption tokens must into account -- together
-   with the bits of information that Issuers may learn about Clients
-   otherwise.  Since this metadata may be useful for practical
+   For this reason, deployments should take the amount of metadata used
+   by an Issuer in creating redemption tokens must into account --
+   together with the bits of information that Issuers may learn about
+   Clients otherwise.  Since this metadata may be useful for practical
    deployments of Privacy Pass, Issuers must balance this against the
    reduction in Client privacy.
 
-   The number of permitted metadata values often depends on deployment
+   The number of permitted metadata values often depends on deployment-
    specific details.  In general, limiting the amount of metadata
    permitted helps limit the extent to which metadata can uniquely
    identify individual Clients.  Failure to bound the number of possible