From 7a83dc933fd5cdd9ef4f3a501c9d4c33c5c8d53e Mon Sep 17 00:00:00 2001
From: Domenic Denicola <d@domenic.me>
Date: Thu, 20 Feb 2020 16:09:08 -0500
Subject: [PATCH] Editorial: tweak wording on no-parameters

Closes #78.
---
 index.src.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.src.html b/index.src.html
index a48456c..3d8ca76 100644
--- a/index.src.html
+++ b/index.src.html
@@ -310,7 +310,7 @@ <h3 id="origin-policy-header">The `<code>Origin-Policy</code>` HTTP header</h3>
 
 <p class="note">If an ID is provided for <code>preferred</code>, it is unnecessary to also include it in the <code>allowed</code> list.</p>
 
-No [=structured header/parameters=] are used in any locations within the structured header.
+This specification does not currently use [=structured header/parameters=] in any locations within the structured header it defines.
 
 The processing model for this header, including the fallback behavior for when it is not provided or does not conform to the above data model, is given in [[#from-response]]. In general, the fallback behavior for malformed headers is to behave the same as if `<code>Origin-Policy: allowed=(null)</code>` is sent, and thus use the [=null origin policy=] for processing the [=response=]. The processing model for omitting the header is to use any previously-cached [=/origin policy=] for the [=/origin=].