Editorial: export definitions needed for Permissions API

Author: marcoscaceres

index.html

@@ -343,7 +343,7 @@ <h3>Algorithms</h3>
 
 <p>Where algorithms that return values are fallible,
  they are written in terms of returning either
- <dfn>success</dfn> or <dfn data-lt=errors>error</dfn>.
+ <dfn class="export" data-local-lt="success">WebDriver success</dfn> (success) or <dfn data-local-lt="error" class="export">WebDriver error</dfn> (error).
  A <a>success</a> value has an associated <var>data</var> field
  which encapsulates the value returned,
  whereas an <a>error</a> response has an associated <a>error code</a>.
@@ -400,7 +400,7 @@ <h3>Commands</h3>
 <p>
 In response to a <a>command</a>,
 a <a>remote end</a> will run a series of actions
-known as <dfn>remote end steps</dfn>.
+known as <dfn class="export">remote end steps</dfn>.
 These provide the sequences of actions that a <a>remote end</a> takes
 when it receives a particular <a>command</a>.
 </section>
@@ -1090,7 +1090,7 @@ <h3>Errors</h3>
 }</code></pre>
 </aside>
 
-<p>The following table lists each <dfn>error code</dfn>,
+<p>The following table lists each <dfn data-local-lt="error code">WebDriver error code</dfn>,
  its associated <a>HTTP status</a>,
  JSON <code>error</code> code,
  and a non-normative description of the error.
@@ -1134,7 +1134,7 @@ <h3>Errors</h3>
    which is usually the result of an expired or invalid TLS certificate.
 
  <tr>
-  <td><dfn>invalid argument</dfn>
+  <td><dfn class="export" data-local-lt="invalid argument">WebDriver invalid argument</dfn>
   <td>400
   <td><code>invalid argument</code>
   <td>The arguments passed to a <a>command</a>
@@ -1344,12 +1344,12 @@ <h3>Extensions</h3>
  features.
 
 <p>Commands defined in this way
- are called <dfn data-lt="extension command">extension commands</dfn>
+ are called <dfn class="export" data-local-lt="extension commands">WebDriver extension commands</dfn>
  and behave no differently than other <a>commands</a>;
  each has a dedicated HTTP endpoint and a set of <a>remote end steps</a>.
 
 <p>Each <a>extension command</a> has an associated
- <dfn>extension command URI Template</dfn>
+ <dfn class="export">extension command URI Template</dfn>
  that is a <a>URI Template</a> string,
  and which should bear some resemblance to what the command performs.
  This value,
@@ -2146,7 +2146,7 @@ <h2>Sessions</h2>
  and allowing sessions to be routed via a multiplexer
  (known as an <a>intermediary node</a>).
 
-<p>A WebDriver <dfn data-lt="sessions">session</dfn> represents
+<p>A <dfn class="export" data-local-lt="session">WebDriver session</dfn> represents
  the <a>connection</a> between a <a>local end</a> and a specific <a>remote end</a>.
 
 <p>A <a>session</a> is started when