commands: correct definition of remote end steps

Remote ends steps are run against all types of remote ends, not
just browsers.

Author: andreastt

index.html

@@ -386,22 +386,25 @@ <h3>Algorithms</h3>
   the result of calling <code>JSON.</code><a>[[\Parse]]</a>(<var>text</var>).
 </section> <!-- /Algorithms -->
 
+
 <section>
 <h3>Commands</h3>
 
-<p>The WebDriver protocol is organised into <a>commands</a>.
- Each <a>HTTP request</a> with a method and template defined in this specification
- represents a single <dfn data-lt="commands">command</dfn>,
- and therefore each command produces a single <a>HTTP response</a>.
- In response to a <a>command</a>,
- a <a>remote end</a> will run a series of actions against the browser.
-
-<p>Each <a>command</a> defined in this specification
- has an associated list of <dfn>remote end steps</dfn>.
- This provides the sequence of actions that a <a>remote end</a> takes
- when it receives a particular <a>command</a>.
+<p>
+The WebDriver protocol is organised into <a>commands</a>.
+Each <a>HTTP request</a> with a method and template defined in this specification
+represents a single <dfn data-lt=commands>command</dfn>,
+and therefore each command produces a single <a>HTTP response</a>.
+
+<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>.
+These provide the sequences of actions that a <a>remote end</a> takes
+when it receives a particular <a>command</a>.
 </section>
 
+
 <section>
 <h3>Processing model</h3>