1 files changed, 2 insertions, 2 deletions

diff --git a/docs/NGIW.Commands.html b/docs/NGIW.Commands.html
index 171df7a..c058a6f 100644
--- a/docs/NGIW.Commands.html
+++ b/docs/NGIW.Commands.html
@@ -10,7 +10,7 @@
 <ul>
 <li>PUT /obj/<strong>oid</strong>/eq -- adds a new event to the queue (at the end)</li>
 <li>PUT /obj/<strong>oid</strong>/eq/0 -- adds a new event to the queue at the <strong>beginning</strong></li>
-<li>PUT /obj/<strong>oid</strong>/eq/9 -- same behavior as PUT /obj/<strong>oid</strong>/eq</li>
+<li>PUT /obj/<strong>oid</strong>/eq/9 -- same behaviour as PUT /obj/<strong>oid</strong>/eq</li>
 <li>GET /obj/<strong>oid</strong>/eq -- returns the full event queue</li>
 <li>PUT /obj/<strong>oid</strong>/eq/<strong>eventid</strong> -- changes the event (or adds one) with id <strong>eventid</strong></li>
 <li>GET /obj/<strong>oid</strong>/eq/<strong>eventid</strong> -- returns the event with id <strong>eventid</strong> or an error</li>
@@ -34,7 +34,7 @@
    
    {"touch_start":{"force":13,"avy":"uuid","time":1311663233}}
 </pre>
-<p>So you can see it is fairly heavy weight compared to a tuned command language. I will investigate what subsequent requests look like when using the http 1.1 persistent connection features. At the worst the http overhead can be amortized across many commands by using the last two forms of request. The last would look like:</p>
+<p>So you can see it is fairly heavy weight compared to a tuned command language. I will investigate what subsequent requests look like when using the http 1.1 persistent connection features. At the worst the http overhead can be amortised across many commands by using the last two forms of request. The last would look like:</p>
 <pre>   PUT /eq HTTP/1.1
    Host: sim.ulat.or
    Content-Type: application/json