Skip to content

Commit

Permalink
missed a few comments
Browse files Browse the repository at this point in the history
  • Loading branch information
dmurph committed Oct 29, 2020
1 parent 76f5ec1 commit a70561e
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,7 @@ <h3>
</p>
<pre class="example json" title="Advanced display usage manifest">
{
"name": "Recipe Madness",
"name": "Recipe Zone",
"description": "All of the recipes!",
"icons": [{
"src": "icon/hd_hi",
Expand Down Expand Up @@ -598,7 +598,7 @@ <h2>
mode</a>.
</p>
<p>
The fallback chain for:
The <dfn>fallback chain</dfn> for:
<ol>
<li>
{{browser}} is «{{browser}}».
Expand Down Expand Up @@ -639,7 +639,7 @@ <h2>
</li>
<li>
[=list/For each=] |fallback_mode:DisplayModeType| of the
fallback chain of |manifest|.{{WebAppManifest/display}}:
[=fallback chain=] of |manifest|.{{WebAppManifest/display}}:
<ol>
<li>
If the user agent supports the |fallback_mode|, then
Expand All @@ -651,13 +651,13 @@ <h2>
</ol>
<p class="note">
The above loop is guaranteed to return a value before the assertion,
due to the fact that {{browser}} is in every mode's fallback chain,
and the requirement that all user agents support the {{browser}}
[=display mode=].
due to the fact that {{browser}} is in every mode's
[=fallback chain=], and the requirement that all user agents support
the {{browser}} [=display mode=].
</p>
<p class="note">
In the future, new values added to {{DisplayModeType}} will not be
added to the fallback chain, and the algorithm should treat these
added to the [=fallback chain=], and the algorithm should treat these
values, when used with the {{WebAppManifest/display}} field, as
{{browser}}. New values will only be compatible with
{{WebAppManifest/display_override}}.
Expand Down

0 comments on commit a70561e

Please sign in to comment.