Wording tweaks for annevk@ feedback

Author: RByers

dom.bs

@@ -737,7 +737,7 @@ inherits from the {{Event}} interface.
 
  <dt><code><var>event</var> . {{Event/defaultPrevented}}</code>
  <dd>Returns true if
- {{Event/preventDefault()}} was used successfully to indicate cancellation.
+ {{Event/preventDefault()}} was invoked successfully to indicate cancellation.
 
  <dt><code><var>event</var> . {{Event/isTrusted}}</code>
  <dd>Returns true if <var>event</var> was
@@ -822,9 +822,9 @@ method must set the <a>canceled flag</a> if the
 the <a>in passive listener flag</a> is unset.
 
 <p class="note no-backref">
- User agents are encouraged to generate a console warning or other debugging
- aid to help authors identify places where calls to {{preventDefault()}}
- have no effect.
+ This means there are scenarios where invoking {{preventDefault()}} has no effect.
+ User agents are encouraged to log the precise cause in a developer console,
+ to aid debugging
 </p>
 
 The
@@ -1017,7 +1017,7 @@ seen from the definition above, an <a>event listener</a> is a more broad concept
   is <var>type</var>. The <var>callback</var> argument sets the <b>callback</b> that will
   be invoked when the <a>event</a> is <a>dispatched</a>.
 
-  The <var>options</var> argument sets listener-specific options.  For compatibility this can be
+  The <var>options</var> argument sets listener-specific options. For compatibility this can be
   just a boolean, in which case the method behaves exactly as if the value was
   specified as <var>options</var>' <code>capture</code> member.
 
@@ -1049,13 +1049,9 @@ seen from the definition above, an <a>event listener</a> is a more broad concept
  {{Event/preventDefault()}} method was not invoked, and false otherwise.
 </dl>
 
-<p>The
-<dfn method for=EventTarget><code>addEventListener(<var>type</var>, <var>callback</var>, <var>options</var>)</code></dfn>
-method, when invoked, must run these steps:
+<p>To <dfn export for=Event id=concept-normalize-options>normalize</dfn> <var>options</var> run these steps:
 
 <ol>
- <li><p>If <var>callback</var> is null, terminate these steps.
-
  <li>Let <var>capture</var> and <var>passive</var> be false.
 
  <li>If <var>options</var> is a boolean, set <var>capture</var> to
@@ -1067,6 +1063,18 @@ method, when invoked, must run these steps:
  <li>If <var>options</var> is a dictionary and <code>{{EventListenerOptions/passive}}</code> is
  present in <var>options</var> with value true, then set <var>passive</var> to true.
 
+ <li>Return <var>capture</var> and <var>passive</var>.
+</ol>
+
+<p>The
+<dfn method for=EventTarget><code>addEventListener(<var>type</var>, <var>callback</var>, <var>options</var>)</code></dfn>
+method, when invoked, must run these steps:
+
+<ol>
+ <li><p>If <var>callback</var> is null, terminate these steps.
+
+ <li>Let <var>capture</var> and <var>passive</var> be the result of <a>normalizing</a> <var>options</var>.
+
  <li><p>Append an <a>event listener</a> to the associated list of <a>event listeners</a> with
  <b>type</b> set to <var>type</var>, <b>callback</b> set to <var>callback</var>, <b>capture</b>
  set to <var>capture</var>, and <b>passive</b> set to <var>passive</var> unless there
@@ -1079,16 +1087,7 @@ method, when invoked, must run these steps:
 method, when invoked, must, run these steps
 
 <ol>
- <li>Let <var>capture</var> and <var>passive</var> be false.
-
- <li>If <var>options</var> is a boolean, set <var>capture</var> to
- <var>options</var>.
-
- <li>If <var>options</var> is a dictionary and <code>{{EventListenerOptions/capture}}</code> is
- present in <var>options</var> with value true, then set <var>capture</var> to true.
-
- <li>If <var>options</var> is a dictionary and <code>{{EventListenerOptions/passive}}</code> is
- present in <var>options</var> with value true, then set <var>passive</var> to true.
+ <li>Let <var>capture</var> and <var>passive</var> be the result of <a>normalizing</a> <var>options</var>.
 
  <li>If there is an <a>event listener</a> in the associated list of
  <a>event listeners</a> whose <b>type</b> is <var>type</var>, <b>callback</b> is <var>callback</var>,
@@ -1113,25 +1112,25 @@ invoked, must run these steps:
 <h3 id=observing-event-listeners>Observing event listeners</h3>
 
 <p>In general, developers do not expect the presence of an <a>event listener</a> to be
-observable.  The impact of an <a>event listener</a> is determined by its <b>callback</b>.
+observable. The impact of an <a>event listener</a> is determined by its <b>callback</b>.
 That is, a developer adding a no-op <a>event listener</a> would not expect it to have
 any side effects.
 
 <p>Unfortunately, some event APIs have been designed such that implementing them
-efficiently requires observing <a>event listeners</a>.  This can make the presence
+efficiently requires observing <a>event listeners</a>. This can make the presence
 of listeners observable in that even empty listeners can have a dramatic performance impact
 on the behavior of the application. For example, touch and wheel events which can be used to block
-asynchronous scrolling.  In some cases this problem can be mitigated by specifying
+asynchronous scrolling. In some cases this problem can be mitigated by specifying
 the event to be {{Event/cancelable}} only when there is at least one
-non-{{EventListenerOptions/passive}} listener.  For example, non-{{EventListenerOptions/passive}}
+non-{{EventListenerOptions/passive}} listener. For example, non-{{EventListenerOptions/passive}}
 {{TouchEvent}} listeners must block scrolling, but if all listeners are {{EventListenerOptions/passive}} then
 scrolling can be allowed to start <a>in parallel</a> by making the {{TouchEvent}}
-uncancelable (so that calls to {{Event/preventDefault()}} are ignored).  So code
+uncancelable (so that calls to {{Event/preventDefault()}} are ignored). So code
 dispatching an event is able to observe the absence of non-{{EventListenerOptions/passive}}
 listeners, and use that to clear the {{Event/cancelable}} property of the event
 being dispatched.
 
-<p>Ideally, any new event types are defined such that they don't need this
+<p>Ideally, any new event APIs are defined such that they do not need this
 property (use <a href="https://lists.w3.org/Archives/Public/public-script-coord/">[email protected]</a>
 for discussion).