srfi-64.html: Fix typos.

Author: apteryks

srfi-64.html

@@ -37,7 +37,7 @@ <h2>Abstract</h2>
 This defines an API for writing <dfn>test suites</dfn>, to make it easy
 to portably test Scheme APIs, libraries, applications, and implementations.
 A test suite is a collection of <dfn>test cases</dfn> that execute
-in the context of a <dfn>test-runner</dfn>.  This specifications
+in the context of a <dfn>test-runner</dfn>.  This specification
 also supports writing new test-runners, to allow customization
 of reporting and processing the result of running test suites.</p>
 
@@ -273,7 +273,7 @@ <h4>Test groups and paths</h4>
 <p>A <code>test-begin</code> enters a new test group.
 The <var>suite-name</var> becomes the current test group name,
 and is added to the end of the test group path.
-Portable test suites should use a sting literal for <var>suite-name</var>;
+Portable test suites should use a string literal for <var>suite-name</var>;
 the effect of expressions or other kinds of literals is unspecified.</p>
 <p>
 <b>Rationale:</b> In some ways using symbols would be preferable.
@@ -370,7 +370,7 @@ <h3>Test suites</h3>
 <h3>Conditonal test-suites and other advanced features</h3>
 <p>
 The following describes features for controlling which tests to execute,
-or specifing that some tests are <em>expected</em> to fail.</p>
+or specifying that some tests are <em>expected</em> to fail.</p>
 
 <h4>Test specifiers</h4>
 <p>Sometimes we want to only run certain tests, or we know that
@@ -390,7 +390,7 @@ <h4>Test specifiers</h4>
 <p>
 <code>(<b>test-match-name</b> <var>name</var>)</code><br />
 The resulting specifier matches if the current test name (as
-returned by <code>test-runner-test-name</code>) is <code>equals?</code> to
+returned by <code>test-runner-test-name</code>) is <code>equal?</code> to
 <var>name</var>.</p>
 <p>
 <code>(<b>test-match-nth</b> <var>n</var> [<var>count</var>])</code><br />
@@ -478,7 +478,7 @@ <h3>Test-runner</h3>
 A <dfn>test-runner</dfn> is an object that runs a test-suite,
 and manages the state.  The test group path, and the sets skip and
 expected-fail specifiers are part of the test-runner.
-A test-runner will also typically accumulate statistics about executed tests,
+A test-runner will also typically accumulate statistics about executed tests.
 </p>
 <p>
 <code>(<b>test-runner?</b> <var>value</var>)</code><br />
@@ -495,7 +495,7 @@ <h3>Test-runner</h3>
 that uses a fluid or thread-local variable, or a plain global variable.</p>
 <p>
 <code>(<b>test-runner-get</b>)</code><br />
-Same as <code>(test-runner-current)</code>, buth throws an exception
+Same as <code>(test-runner-current)</code>, but throws an exception
 if there is no current test-runner.</p>
 <p>
 <code>(<b>test-runner-simple</b>)</code><br />
@@ -536,7 +536,7 @@ <h4>Running specific tests with a specified runner</h4>
 <code>test-apply</code> <em>and</em> does not match any
 active <code>test-skip</code> specifiers.</p>
 <p>
-<code>(<b>test-with-runner </b><var>runner</var> <var>decl-or-expr</var> ...)</code><br />
+<code>(<b>test-with-runner</b><var>runner</var> <var>decl-or-expr</var> ...)</code><br />
 Executes each <var>decl-or-expr</var> in order in a context
 where the current test-runner is <var>runner</var>.</p>
 
@@ -557,11 +557,11 @@ <h4>Result kind</h4>
 </dl>
 <p>
 <code>(<b>test-result-kind</b> [<var>runner</var>])</code><br />
-Return one of the above result codes from the most recent tests.
+Returns one of the above result codes from the most recent tests.
 Returns <code>#f</code> if no tests have been run yet.
 If we've started on a new test, but don't have a result yet,
-then the result kind is <code>'xfail</code> is the test is expected to fail,
-<code>'skip</code> is the test is supposed to be skipped,
+then the result kind is <code>'xfail</code> if the test is expected to fail,
+<code>'skip</code> if the test is supposed to be skipped,
 or <code>#f</code> otherwise.</p>
 <p>
 <code>(<b>test-passed?</b> [<var>runner</var>])</code><br />
@@ -622,7 +622,7 @@ <h4>Standard result properties</h4>
 <dt><code>'source-file</code></dt>
 <dt><code>'source-line</code></dt>
 <dd>If known, the location of test statements (such as <code>test-assert</code>)
-in test suite source code..</dd>
+in test suite source code.</dd>
 <dt><code>'source-form</code></dt>
 <dd>The source form, if meaningful and known.</dd>
 <dt><code>'expected-value</code></dt>