Fix a couple of typos

CONTRIBUTING.md

@@ -131,7 +131,7 @@ end you contribute to `ppb` by being part of its community.
 [fork]: https://help.github.com/articles/fork-a-repo/ "Fork a repo"
 [goals]: https://ppb.dev/#guiding-principles "PPB Goals"
 [issues]: https://github.com/ppb/pursuedpybear/issues "PPB Issues"
-[new contributor]: https://github.com/ppb/pursuedpybear/labels/new%20contributor "Issues labeld New Contributor"
+[new contributor]: https://github.com/ppb/pursuedpybear/labels/new%20contributor "Issues labeled New Contributor"
 [projects]: https://github.com/orgs/ppb/projects "PPB Projects"
 [readme]: https://github.com/ppb/pursuedpybear/blob/canon/README.md "PPB README"
 [tutorial]: https://github.com/ppb/tutorials "PPB Tutorials"

CONTRIBUTORS.md

@@ -37,4 +37,5 @@ Halle Jones|HJones@aliacy.com||
 [Mfon Eti-mfon](https://github.com/mfonism) | [mfon@etimfon.com](mfon@etimfon.com) | [mfonism](https://twitter.com/mfonism)
 [Regina Reynolds](https://github.com/reginareynolds) | [regina.c.reynolds@gmail.com](regina.c.reynolds@gmail.com)
 [Ian Clark](https://github.com/ace510) | [ianhclark510@gmail.com] | [ianhclark510](https://twitter.com/ianhclark510)
-[Casey Faist](https://github.com/caseyfaist) |  | [cfactoid](https://twitter.com/cfactoid)
+[Casey Faist](https://github.com/caseyfaist) |  | [cfactoid](https://twitter.com/cfactoid)
+[Jürgen Gmach](https://jugmac00.github.io/) | [juergen.gmach@googlemail.com](juergen.gmach@googlemail.com) | [@jugmac00](https://twitter.com/jugmac00)

README.md

@@ -109,5 +109,5 @@ discussions.](https://github.com/ppb/pursuedpybear/issues?q=is%3Aissue+is%3Aopen
 If you're already using `ppb` feel free to report bugs, suggest
 enhancements, or ask for new features.
 
-If you want to contribute code, definitely read the relavant portions
+If you want to contribute code, definitely read the relevant portions
 of Contributing.MD

ROADMAP.md

@@ -33,7 +33,7 @@ working better.
 
 To really make this a teaching tool, it's going to require a visual editor.
 Because this is Python and I can do it, I'd like to make the editor using the 
-engine. As such, it's going to be built in in conjunction to the engine itself.
+engine. As such, it's going to be built in conjunction to the engine itself.
 
 ### Object editor
 
@@ -51,7 +51,7 @@ The primary workflow should give an idea of how scenes are being used.
 
 Introduce a concept of a sub-scene (outside the context of code)
 
-## Packagine System
+## Packaging System
 
 This is the nice to have, but I'd like to make it possible for a person to 
 build the entire game via the visual editor and output functional python that

docs/discussion/assets.rst

@@ -55,7 +55,7 @@ Then, you make an :py:class:`Asset` subclass. There's a few methods of note for
 
 * :py:meth:`Asset.background_parse()`: Do the actual parsing. Accepts the bytes loaded from the file, and returns the data object that the asset is wrapping.
 * :py:meth:`Asset.file_missing()`: If defined, this will be called if the file is not found, and is expected to return a synthesized stand-in object. If not defined, :py:meth:`Asset.load()` will raise an error.
-* :py:meth:`Asset.free()`: Handles cleanup in the case where resources need to be explicitly cleaned. Note that because this is called in the context of :py:meth:`__del__() <object.__del__>`, care must be taken around refering to globals or other modules.
+* :py:meth:`Asset.free()`: Handles cleanup in the case where resources need to be explicitly cleaned. Note that because this is called in the context of :py:meth:`__del__() <object.__del__>`, care must be taken around referring to globals or other modules.
 
 At the point of use, all you need to do is call :py:meth:`Asset.load()` and you will get the object created by the asset. This will block if the background processing is incomplete.
 

docs/reference/assets.rst

@@ -56,7 +56,7 @@ You should really only implement three methods:
   needed to turn a pile of bytes into a useful data structure.
 
 * :py:meth:`file_missing()`: This is called if the asset is not found. Defining
-  this method surpresses :py:meth:`load()` from raising a
+  this method suppresses :py:meth:`load()` from raising a
   :py:exc:`FileNotFoundError` and will instead call this, and
   :py:meth:`load()` will return what this returns.
 

examples/two-phase-updates/three_body.py

@@ -3,7 +3,7 @@
 two-phase updates.
 
 The three body problem comes from astrophysics. Basically, applying the
-gravitaional to three celestial bodies produces a problem that does not have a
+gravitational to three celestial bodies produces a problem that does not have a
 perfect mathematical solution, and must be solved through simulations.
 """
 

ppb/assetlib.py

@@ -123,7 +123,7 @@ def queued_events(self):
 
 class MockFuture(concurrent.futures.Future):
     """
-    Acts as a Future's understudy until the real future is availalble.
+    Acts as a Future's understudy until the real future is available.
     """
     _handed_off = False
 

viztests/soundonly.py

@@ -1,5 +1,5 @@
 """
-Tests the sound system without initializating anything else.
+Tests the sound system without initializing anything else.
 
 NOTE: Does not open a window.
 """