Overview.src.html
changeset 35 baec5d686215
parent 34 c0cf2410619b
child 36 41c928b92c07
--- a/Overview.src.html	Wed Apr 16 16:19:50 2014 -0700
+++ b/Overview.src.html	Wed Apr 30 13:44:55 2014 -0700
@@ -319,7 +319,7 @@
  the <span>display steps</span> and terminate these steps.
 
  <li><p>If the device has limitations on the number of concurrent
- notifications, either immediately call to a notifications platform which
+ notifications, either immediately call to a notification platform which
  natively supports queueing, or append <var title>notification</var> to the
  <span>list of pending notifications</span>.
 </ol>
@@ -328,7 +328,7 @@
 
 <p>When a <span title=concept-notification>notification</span>
 <var title>notification</var> is activated by the user, assuming the underlying
-notifications platform supports activation, the user agent must, for each
+notification platform supports activation, the user agent must, for each
 <code>Notification</code> object representing <var title>notification</var>,
 <span data-anolis-spec=html>queue a task</span> to
 <span data-anolis-spec=dom title=concept-event-fire>fire an event</span>
@@ -339,7 +339,7 @@
 <h3>Closing a notification</h3>
 
 <p>When a <span title=concept-notification>notification</span> is closed,
-either by the underlying notifications platform or by the user, the
+either by the underlying notification platform or by the user, the
 <span>close steps</span> for it must be run.
 
 <p>The <dfn>close steps</dfn> for a given <var title>notification</var> are: