Explicitly call out cookie clearing for an origin.

index.html

@@ -2018,8 +2018,8 @@ <h2 class="heading settled" data-level="6" id="privacy-and-security"><span class
    <h3 class="heading settled" data-level="6.1" id="tracking"><span class="secno">6.1. </span><span class="content">Tracking</span><a class="self-link" href="#tracking"></a></h3>
    <p>The <a data-link-type="dfn" href="#origin-policy" id="ref-for-origin-policy-8"><code>Origin-Policy</code></a> header, as well as the manifest it represents, can
 be used to track users with only marginally less granularity and coverage than
-cookies allow. As such, the user agent MUST purge cached manifests whenever a
-user instructs it to clear cookies or cached data.</p>
+cookies allow. As such, the user agent MUST purge an origin’s cached manifests
+whenever a user instructs it to clear cookies or cached data for that origin.</p>
    <h2 class="heading settled" data-level="7" id="iana"><span class="secno">7. </span><span class="content">IANA Considerations</span><a class="self-link" href="#iana"></a></h2>
    <h3 class="heading settled" data-level="7.1" id="iana-header"><span class="secno">7.1. </span><span class="content">The <code>Origin-Policy</code> header</span><a class="self-link" href="#iana-header"></a></h3>
    <p>The permanent message header field registry should be updated

index.src.html

@@ -781,8 +781,8 @@ <h4 algorithm dfn id="fetch-apply-policy">
 
 The <a>`Origin-Policy`</a> header, as well as the manifest it represents, can
 be used to track users with only marginally less granularity and coverage than
-cookies allow. As such, the user agent MUST purge cached manifests whenever a
-user instructs it to clear cookies or cached data.
+cookies allow. As such, the user agent MUST purge an origin's cached manifests
+whenever a user instructs it to clear cookies or cached data for that origin.
 
 IANA Considerations {#iana}
 ===================