Incorporate Josh Soref's spelling and grammar fixes. default tip
authorEdward O'Connor <eoconnor@apple.com>
Mon, 17 Aug 2015 13:04:36 -0700
changeset 48 e96213df027d
parent 47 0c0d48a076a5
Incorporate Josh Soref's spelling and grammar fixes.
Overview.src.html
--- a/Overview.src.html	Wed Jun 10 21:03:22 2015 +0900
+++ b/Overview.src.html	Mon Aug 17 13:04:36 2015 -0700
@@ -154,12 +154,10 @@
 <h2>Introduction</h2>
 
 <p>This specification provides an API to display notifications to alert
-users outside the context of a web page. It does not specify exactly how a
-user agent should display these notifications; the best presentation depends
-on the device where the user agent is run. When this specification refers
-to displaying notifications on the "desktop", it generally refers to some
-static display area outside the web page, but may take several forms,
-including:
+users outside the context of a web page. When this specification refers
+to displaying notifications on the "desktop", it generally refers to
+some static display area outside the web page, but that may take several
+forms, including:
 
 <ul>
  <li>A corner of the user's display.
@@ -167,15 +165,16 @@
  <li>The "home" screen of a mobile device.
 </ul>
 
-<p>This specification does not define exactly how the user agent should
-display the notification, and the API is designed to be flexible with
-respect to presentation options.
+<p>It does not specify exactly how a user agent should display these
+notifications; the best presentation depends on the device where the
+user agent is run. The API is designed to be flexible with respect to
+presentation options.
 
 <p>This specification is designed to be compatible with existing
 notification platforms as much as possible, but also to be
 platform-independent. Since the common platforms do not provide the same
 functionality, this spec will indicate what events are guaranteed and
-which are not. In particular, notifications as specified here only can
+which are not. In particular, notifications as specified here can only
 contain text and icon content.
 
 <p>In general, the event model for notifications is best-effort; while the
@@ -221,7 +220,7 @@
 <h2>Model</h2>
 
 <p>A <dfn title=concept-notification>notification</dfn> allows alerting the
-user outside the context of a web page of an occurrence, such as the
+user outside the context of a web page that something happened, such as the
 delivery of email.
 
 <p>Each <span title=concept-notification>notification</span> has a
@@ -235,6 +234,7 @@
 <p class=note>Developers are encouraged to not convey information
 through an icon, sound, or vibration pattern that is not otherwise
 accessible to the end user.
+See <a href="http://www.w3.org/WAI/intro/wcag">WCAG</a> for more.
 
 <h3>Direction</h3>
 
@@ -249,7 +249,7 @@
 and <span>body</span>. Each is expected to be treated as an independent set
 of one or more bidirectional algorithm paragraphs when displayed, as defined
 by the bidirectional algorithm's rules P1, P2, and P3, including, for
-instance, supporting the paragraph-breaking behaviour of
+instance, supporting the paragraph-breaking behavior of
 U+000A LINE FEED (LF) characters. For each paragraph of the
 <span>title</span> and <span>body</span>, the
 <span title=concept-notification>notification</span>'s
@@ -342,7 +342,7 @@
 <p>When a <span title=concept-notification>notification</span>
 <var title>notification</var> is activated by the user, assuming the underlying
 notification platform supports activation, the user agent must, for each
-<code>Notification</code> object representing <var title>notification</var>,
+<code>Notification</code> object <a href="#tags-example">representing <var title>notification</var></a>,
 <span data-anolis-spec=html>queue a task</span> to
 <span data-anolis-spec=dom title=concept-event-fire>fire an event</span>
 named <code title>click</code> on the <code>Notification</code> object.
@@ -402,16 +402,15 @@
   be fully downloaded.
 
   <p>Once <span data-anolis-spec=html title=fetch>fetching</span> has
-  finished and the image format is supported, set
+  finished and if the image format is supported, set
   <var title>notification</var>'s <span>icon image</span> to the decoded resource.
-  (Otherwise <var title>notification</var> has no <span>icon image</span>.)
 
  <li>
   <p><span data-anolis-spec=html>Queue a task</span> to run these substeps:
 
   <ol>
    <li><p>Display <var title>notification</var> on the device (e.g. by
-   calling the appropriate notification platform).
+   making the appropriate notification platform API call).
 
    <li><p>If displaying fails (e.g. the notification platform returns an
    error),
@@ -445,7 +444,6 @@
   <p>Once <span data-anolis-spec=html title=fetch>fetching</span> has
   finished and the image format is supported, set
   <var title>new</var>'s <span>icon image</span> to the decoded resource.
-  (Otherwise <var title>new</var> has no <span>icon image</span>.)
 
  <li><p>If <var title>old</var> is in the
  <span>list of pending notifications</span>,
@@ -542,8 +540,8 @@
  <li><p>If <var title>options</var>'s <code title>lang</code> is a valid
  BCP 47 language tag, or the empty string, set
  <var title>notification</var>'s <span>language</span> to
- <var title>options</var>'s <code title>lang</code>, or set it to the empty
- string otherwise. <span data-anolis-ref>LANG</span>
+ <var title>options</var>'s <code title>lang</code>. Otherwise, set it
+ to the empty string. <span data-anolis-ref>LANG</span>
 
  <li><p>Set <var title>notifications</var>'s <span>origin</span> to the
  current <span data-anolis-spec=html>origin</span>.
@@ -560,15 +558,16 @@
  <code title>icon</code> using the <span data-anolis-spec=html>API base URL</span>
  specified by the <span data-anolis-spec=html>entry settings object</span>, and if that
  does not return failure, set <var title>notification</var>'s <span>icon URL</span> to the
- return value. (Otherwise <span>icon URL</span> is not set.)
+ return value.
 
  <li><p>Return <var title>notification</var>, but continue running these
- steps asynchronouusly.
+ steps asynchronously.
 
- <li><p>If the notification platform supports icons, the user agent may
- start <span data-anolis-spec=html title=fetch>fetching</span>
- <var title>notification</var>'s <span>icon URL</span> at this point, if
- <span>icon URL</span> is set.
+ <li><p>If <span>icon URL</span> is set and the notification platform
+ supports icons, the user agent may start <span data-anolis-spec=html
+ title=fetch>fetching</span>
+ the <var title>notification</var>'s <span>icon URL</span> at this
+ point.
 
  <li><p>Run the <span>show steps</span> for <var title>notification</var>.
 </ol>
@@ -646,8 +645,8 @@
 string otherwise.
 
 <p>The <dfn title=dom-Notification-tag><code>tag</code></dfn> attribute must return the
-<span title=concept-notification>notification</span>'s <span>tag</span> and the empty
-string otherwise.
+<span title=concept-notification>notification</span>'s <span>tag</span> or the empty
+string if it has no tag.
 
 <p>The <dfn title=dom-Notification-icon><code>icon</code></dfn> attribute must return the
 <span title=concept-notification>notification</span>'s <span>icon URL</span>,
@@ -755,6 +754,7 @@
 James Graham,
 Jon Lee,
 Jonas Sicking,
+Josh Soref,
 Michael Cooper,
 Michael Henretty,
 Olli Pettay, and