address Anne's LC feedback <http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0016.html>
--- a/proximity/Overview.html Fri Dec 07 11:36:05 2012 +0200
+++ b/proximity/Overview.html Fri Dec 07 15:59:34 2012 +0200
@@ -223,20 +223,17 @@
</li>
</ol>
</li>
- <li>
- <a>Queue a task</a> to dispatch the newly created event at the
- <a>Window</a> object.
- </li>
</ol>
<p>
- When <a>the current proximity</a> changes, the <dfn>user
- agent</dfn> MUST <a>fire a device proximity event</a>.
+ When the <a>current device proximity</a> changes, the <dfn>user
+ agent</dfn> MUST queue a task to <a>fire a device proximity event</a>
+ at the <a>Window</a> object.
</p>
<div class="note">
The definition of granularity i.e. how often the event is fired is
- left to the implementation. Implementations may fire the event if
+ left to the implementation. Implementations can fire the event if
they have reason to believe that the page does not have sufficiently
- fresh data. Different devices may also support different minimum and
+ fresh data. Different devices can also support different minimum and
maximum sensing distances as well as different resolution, thus
authors are strongly advised to use the <a>UserProximityEvent</a>
interface if the are only interested in finding out if the user is
@@ -320,14 +317,11 @@
</li>
</ol>
</li>
- <li>
- <a>Queue a task</a> to dispatch the newly created event at the
- <a>Window</a> object.
- </li>
</ol>
<p>
When the <a>current user proximity state</a> changes, the <dfn>user
- agent</dfn> MUST <a>fire a user proximity event</a>.
+ agent</dfn> MUST queue a task to <a>fire a user proximity event</a>
+ at the <a>Window</a> object.
</p>
<section>
<h2>Event handlers</h2>