References to 'user agent' term corrected.
authorVincent Scheib <scheib@google.com>
Fri, 24 Jan 2014 10:24:27 -0800
changeset 44 30369e8e4860
parent 43 1c24a270ff82
child 45 ea789b4e5b82
References to 'user agent' term corrected.
index.html
--- a/index.html	Fri Jan 24 10:17:30 2014 -0800
+++ b/index.html	Fri Jan 24 10:24:27 2014 -0800
@@ -186,7 +186,7 @@
       and <dfn>pointerlockerror</dfn>. If pointer lock is entered or exited
       for any reason a <a>pointerlockchange</a> event must be sent.</p>
 
-      <p><a>User agents</a>
+      <p><a>User agent</a>s
       must deliver these events by <a
       href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#queue-a-task">
       queuing a task</a> to <a class="external"
@@ -334,7 +334,7 @@
     <section>
       <h2>Extensions to the <a>MouseEvent</a> Interface</h2>
 
-      <p>User agents must extend the MouseEvent interface
+      <p><a>User agent</a>s must extend the MouseEvent interface
       [[!DOM-LEVEL-3-EVENTS]]
       with two members:</p>
 
@@ -387,7 +387,7 @@
     <section>
       <h2>Extensions to the <a>MouseEventInit</a> Dictionary</h2>
 
-      <p>User agents must extend the MouseEventInit dictionary
+      <p><a>User agent</a>s must extend the MouseEventInit dictionary
       [[!DOM-LEVEL-3-EVENTS]] with two members <code>movementX</code> and
       <code>movementY</code> used to initialize respective members
       of <code>MouseEvent</code>.</p>
@@ -406,7 +406,7 @@
       <p>A <dfn>default unlock gesture</dfn> must always be available that
       will exit pointer lock.</p>
       <p class="note">The ESC key is the recommended <a>default unlock
-      gesture</a> for user agents with keyboard input. It is recommended that
+      gesture</a> for <a>user agent</a>s with keyboard input. It is recommended that
       the unlock gesture also match any used to exit fullscreen
       [[FULLSCREEN]].</p>
 
@@ -421,7 +421,7 @@
 
       <p>Pointer lock must not be exited when fullscreen [[FULLSCREEN]] is
       entered or exited unless the pointer is required to enable interaction
-      with the user agent graphical user interface or the <a>default
+      with the <a>user agent</a> graphical user interface or the <a>default
       unlock gesture</a> was used to exit both fullscreen and pointer
       lock.</p>
     </section>
@@ -568,16 +568,16 @@
           <li>Pointer Lock can be called repeated by script after user exits pointer
           lock, blocking user from meaningful progress.</li>
 
-          <li>Full screen exit instructions are displayed in some <a>user agents</a> when
+          <li>Full screen exit instructions are displayed in some <a>user agent</a>s when
           the pointer is moved to the top of the screen.  During pointer lock that
           gesture is not possible.</li>
         </ul>
 
         <p>Responses:</p>
         <ul>
-          <li>User agents may limit what security origins may lock the pointer.</li>
+          <li><a>User agent</a>s may limit what security origins may lock the pointer.</li>
 
-          <li>User agents may prompt for confirmation before locking, this
+          <li><a>User agent</a>s may prompt for confirmation before locking, this
           preference may be saved as a content setting.</li>
 
           <li>Escape will always be provided by a <a>default unlock
@@ -607,11 +607,11 @@
         <p>Pointer lock is a required user interaction mode for certain application
         types, but carries a usability concern if maliciously used.  An attacker
         could remove the ability for a user to control their mouse cursor on their
-        system.  User agents will prevent this by always providing a mechanism to
+        system.  <a>User agent</a>s will prevent this by always providing a mechanism to
         exit pointer lock, by informing the user of how, and by limiting how pointer
         lock can be entered.</p>
 
-        <p>User agents will determine their own appropriate policies, which may be
+        <p><a>User agent</a>s will determine their own appropriate policies, which may be
         specialized per device or differ based on user options.
     </section>
 
@@ -686,7 +686,7 @@
         approach.  The first is a concern of specifying what units mouse movement
         data are provided in.  This specification defines .movementX/Y precisely
         as the same values that could be recorded when the mouse is not under lock
-        by changes in .screenX/Y.  Implementations across multiple <a>user agents</a> and
+        by changes in .screenX/Y.  Implementations across multiple <a>user agent</a>s and
         operating systems will easily be able to meet that requirement and provide
         application developers and users with a consistent experience.  Further,
         users are expected to have already configured the full system of hardware