Re: [w3c/manifest] chore: refactor and export scope terms (#882)

@mgiuca commented on this pull request.



> @@ -437,11 +437,11 @@ <h2>
         Navigation scope
       </h2>
       <p data-link-for="WebAppManifest">
-        A <dfn data-export="">navigation scope</dfn> is a <a>URL</a> that
-        represents the set of URLs to which an <a>application context</a> can
-        be navigated while the manifest is <a>applied</a>. The <a>navigation
-        scope</a> of a manifest <var>manifest</var> is
-        <var>manifest</var>["<a>scope</a>"].
+        The {{WebAppManifest/scope}} member of a [=processed manifest=] is the

Nit: I think I'd prefer this to be phrased around the other way to avoid it looking like Yoda wrote it :)

"The **navigation scope** of an application context is the `scope` member of the processed manifest that is applied to it."

(As a bonus: we link this back up to the concept of "applied".)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/882#pullrequestreview-424975707