activation trigger: improve prose and mark isTrusted correctly

The isTrusted reference should be marked with a <code> tag, but
this patch also improves the language in the note associated with
it.

Author: andreastt

index.html

@@ -6928,29 +6928,30 @@ <h3>Ticks</h3>
  <!-- todo: define generating DOM events from an input somewhere -->
 
 <aside class=note>
- <p>An <a>activation trigger</a>
-  generated by the WebDriver API user
-  needs to be indistinguishable from those generated
-  by a real user interacting with the browser.
-  In particular, the dispatched events will have
-  the <a>isTrusted</a> attribute set to true.
-  The most robust way to dispatch these events
-  is by creating them in the browser implementation itself.
-  Sending OS-specific input messages to the browser's window
-  has the disadvantage that the browser being automated
-  may not be properly isolated from a user
-  accidentally modifying <a>input source state</a>.
-  Use of an OS-level accessibility API has the disadvantage
-  that the browser's window must be focused,
-  and as a result, multiple WebDriver instances cannot run in parallel.
-
- <p>An advantage of an OS-level accessibility API
-  is that it guarantees that inputs correctly mirror user input,
-  and allows interaction with the host OS if necessary.
-  This might, however, have performance penalties
-  from a machine utilisation perspective.
-</aside>
+<p>
+An <a>activation trigger</a> generated by WebDriver
+needs to be indistinguishable from those generated by a real user interacting with the browser.
+In particular, the dispatched events
+will have the <a><code>isTrusted</code></a> attribute set to true.
+
+<p>
+The most robust way to despatch these events
+is by creating them in the browser implementation itself.
+Sending operating system specific input messages to the browser’s window
+has the disadvantage that the browser being automated
+may not be properly isolated from a user
+accidentally modifying <a>input source state</a>.
+Use of an operating system level accessibility API
+has the disadvantage that the browser’s window must be focused,
+and as a result, multiple WebDriver instances cannot run in parallel.
 
+<p>
+The advantage of an operating system level accessibility API
+is that it guarantees that inputs correctly mirror user input,
+and allows interaction with the host system if necessary.
+This might, however, have performance penalties
+from a machine utilisation perspective.
+</aside>
 </section> <!-- /Ticks -->
 
 
@@ -9145,7 +9146,7 @@ <h2>Index</h2>
    <!-- hasAttribute --> <li><dfn data-lt="has the attribute"><a href=https://dom.spec.whatwg.org/#dom-element-hasattribute>hasAttribute</a></dfn>
    <!-- HTMLCollection --> <li><dfn><a href=https://dom.spec.whatwg.org/#htmlcollection><code>HTMLCollection</code></a></dfn>
    <!-- Inclusive descendant --> <li><dfn><a href=https://dom.spec.whatwg.org/#concept-tree-inclusive-descendant>Inclusive descendant</a></dfn>
-   <!-- isTrusted --> <li><dfn data-lt='is trusted'><a href="https://dom.spec.whatwg.org/#dom-event-istrusted">isTrusted</a></dfn>
+   <!-- isTrusted --> <li><dfn data-lt='is trusted'><a href="https://dom.spec.whatwg.org/#dom-event-istrusted"><code>isTrusted</code></a></dfn>
    <!-- Node document --> <li><dfn><a href=https://dom.spec.whatwg.org/#concept-node-document>Node document</a></dfn>
    <!-- Node length --> <li><dfn><a href="https://dom.spec.whatwg.org/#concept-node-length">Node Length</a></dfn>
    <!-- Node --> <li><dfn><a href=https://dom.spec.whatwg.org/#concept-node>Node</a></dfn>