update docs for 4.13

[i3/i3.github.io] / docs / testsuite.html

diff --git a/docs/testsuite.html b/docs/testsuite.html
index 409ccf3f836e8e37e84cfe5653231eb0902afc6b..9fa9202743fd9881c9cc376bff7074c750c3e51f 100644 (file)
--- a/docs/testsuite.html
+++ b/docs/testsuite.html
@@ -171,7 +171,7 @@ always be found under the symlink <tt>latest/</tt>. Unless told differently, it
 run the tests on a separate X server instance (using Xephyr).</p></div>\r
 <div class="paragraph"><p>Xephyr will open a window where you can inspect the running test. You can run\r
 the tests without an X session with Xvfb, such as with <tt>xvfb-run\r
-./complete-run</tt>. This will also speed up the tests signficantly especially on\r
+./complete-run</tt>. This will also speed up the tests significantly especially on\r
 machines without a powerful video card.</p></div>\r
 <div class="listingblock">\r
 <div class="title">Example invocation of complete-run.pl+</div>\r
@@ -252,7 +252,7 @@ current state (layout tree).</p></div>
 testsuite uses X11::XCB, a new (and quite specific to i3 at the moment) Perl\r
 module which uses the XCB protocol description to generate Perl bindings to\r
 X11. They work in a very similar way to libxcb (which i3 uses) and provide\r
-relatively high-level interfaces (objects such as <tt>X11::XCB::Window</tt>) aswell as\r
+relatively high-level interfaces (objects such as <tt>X11::XCB::Window</tt>) as well as\r
 access to the low-level interface, which is very useful when testing a window\r
 manager.</p></div>\r
 </div>\r
@@ -492,7 +492,7 @@ my $right = open_window($x);
 cmd 'focus left';\r
 is($x-&gt;input_focus, $left-&gt;id, 'left window focused');</tt></pre>\r
 </div></div>\r
-<div class="paragraph"><p>However, the test fails. Sometimes. Apparantly, there is a race condition in\r
+<div class="paragraph"><p>However, the test fails. Sometimes. Apparently, there is a race condition in\r
 your test. If you think about it, this is because you are using two different\r
 pieces of software: You tell i3 to update focus, i3 confirms that, and then you\r
 ask X11 to give you the current focus. There is a certain time i3 needs to\r
@@ -665,7 +665,7 @@ activation, we decreased the total amount of time necessary to run all tests
 (72 files at the time of writing) from &gt; 100 seconds to 16 seconds. This makes\r
 it significantly more attractive to run the test suite more often (or at all)\r
 during development.</p></div>\r
-<div class="paragraph"><p>An alternative approach to using socket activation is polling for the existance\r
+<div class="paragraph"><p>An alternative approach to using socket activation is polling for the existence\r
 of the IPC socket and connecting to it. While this might be slightly easier to\r
 implement, it wastes CPU time and is considerably uglier than this solution\r
 :). After all, <tt>lib/SocketActivation.pm</tt> contains only 54 SLOC.</p></div>\r