Purposelist consent update.

Signed-off-by: Ulf Bjorkengren <[email protected]>

spec/VISSv2_Core.html

@@ -1627,7 +1627,7 @@ <h2>Purpose List</h2>
         There is also a long purpose description, which may be used in the dialogue for consent, if needed. 
         Then there is a list of the <a href="#client-context-def">client context</a>, i. e. the sub-actor role triplet, 
         that can be granted this access, and last there is a list of  the signals that the client is given access to for this purpose, 
-        with the allowed access permission. The list shall use a JSON format as shown in the example below.
+        with the access control and consent requirements. The list shall use a JSON format as shown in the example below.
         <pre><code>
         {"purposes":
             [{"short": "fuel-status",