Fix spelling errors

.codespellrc

@@ -0,0 +1,2 @@
+[codespell]
+ignore-words-list = crate,ofo

NEWS

@@ -335,7 +335,7 @@ All the other filters now only parse and emit v2 streams. V2 is still in
 draft format, so if you want to delay and wait for v2 to be finalised, you
 should use subunit-2to1 before any serialisation steps take place.
 With the ability to encapsulate multiple non-test streams, another significant
-cange is that filters which emit subunit now encapsulate any non-subunit they
+change is that filters which emit subunit now encapsulate any non-subunit they
 encounter, labelling it 'stdout'. This permits multiplexing such streams and
 detangling the stdout streams from each input.
 

README.md

@@ -49,7 +49,7 @@ A number of useful things can be done easily with subunit:
    can be aggregated into a single stream through a multiplexer.
  * Test archiving: A test run may be recorded and replayed later.
  * Test isolation: Tests that may crash or otherwise interact badly with each
-   other can be run seperately and then aggregated, rather than interfering
+   other can be run separately and then aggregated, rather than interfering
    with each other or requiring an adhoc test->runner reporting protocol.
  * Grid testing: subunit can act as the necessary serialisation and
    deserialiation to get test runs on distributed machines to be reported in
@@ -139,7 +139,7 @@ ways the test framework doesn't apply any semantic value to), file attachments
 
 
 Version 2, or v2 is new and still under development, but is intended to
-supercede version 1 in the very near future. Subunit's bundled tools accept
+supersede version 1 in the very near future. Subunit's bundled tools accept
 only version 2 and only emit version 2, but the new filters subunit-1to2 and
 subunit-2to1 can be used to interoperate with older third party libraries.
 
@@ -166,7 +166,7 @@ damaged data.
 A key design goal for Subunit version 2 is to allow processing and multiplexing
 without forcing buffering for semantic correctness, as buffering tends to hide
 hung or otherwise misbehaving tests. That said, limited time based buffering
-for network efficiency is a good idea - this is ultimately implementator
+for network efficiency is a good idea - this is ultimately implementer
 choice. Line buffering is also discouraged for subunit streams, as dropping
 into a debugger or other tool may require interactive traffic even if line
 buffering would not otherwise be a problem.

c/check-subunit-0.9.5.patch

@@ -84,7 +84,7 @@
 +   enable_subunit=false
 +   ;;
 + true)
-+   AC_MSG_ERROR([The header subunit/child.h could not be succesfully included and is required for subunit protocol support. The homepage for subunit is https://launchpad.net/subunit/])
++   AC_MSG_ERROR([The header subunit/child.h could not be successfully included and is required for subunit protocol support. The homepage for subunit is https://launchpad.net/subunit/])
 +   ;;
 + esac
 +])
@@ -171,7 +171,7 @@
 +
 +Check supports running test suites with subunit output. This can be useful to
 +combine test results from multiple languages, or to perform programmatic
-+analysis on the results of multiple check test suites or otherise handle test
++analysis on the results of multiple check test suites or otherwise handle test
 +results in a programmatic manner. Using subunit with check is very straight
 +forward. There are two steps:
 +1) In your check test suite driver pass 'CK_SUBUNIT' as the output mode

c/check-subunit-0.9.6.patch

@@ -77,7 +77,7 @@
 +   enable_subunit=false
 +   ;;
 + true)
-+   AC_MSG_ERROR([The header subunit/child.h could not be succesfully included and is required for subunit protocol support. The homepage for subunit is https://launchpad.net/subunit/])
++   AC_MSG_ERROR([The header subunit/child.h could not be successfully included and is required for subunit protocol support. The homepage for subunit is https://launchpad.net/subunit/])
 +   ;;
 + esac
 +])
@@ -164,7 +164,7 @@
 +
 +Check supports running test suites with subunit output. This can be useful to
 +combine test results from multiple languages, or to perform programmatic
-+analysis on the results of multiple check test suites or otherise handle test
++analysis on the results of multiple check test suites or otherwise handle test
 +results in a programmatic manner. Using subunit with check is very straight
 +forward. There are two steps:
 +1) In your check test suite driver pass 'CK_SUBUNIT' as the output mode

python/subunit/__init__.py

@@ -851,7 +851,7 @@ def __eq__(self, other):
             return False
 
     def __init__(self, description):
-        """Create a psuedo test case with description description."""
+        """Create a pseudo test case with description description."""
         self.__description = description
 
     def error(self, label):

python/subunit/filter_scripts/subunit_filter.py

@@ -101,7 +101,7 @@ def make_options(description):
         "--rename",
         action="append",
         nargs=2,
-        help="Apply specified regex subsitutions to test names.",
+        help="Apply specified regex substitutions to test names.",
         dest="renames",
         default=[],
     )

python/subunit/v2.py

@@ -257,7 +257,7 @@ class ByteStreamToStreamResult(object):
     """Parse a subunit byte stream.
 
     Mixed streams that contain non-subunit content is supported when a
-    non_subunit_name is passed to the contructor. The default is to raise an
+    non_subunit_name is passed to the constructor. The default is to raise an
     error containing the non-subunit byte after it has been read from the
     stream.