Run codespell.

INSTALL

@@ -31,7 +31,7 @@ headers reside. The recommended way to get the Lua libraries is to download the
 
   http://luabinaries.luaforge.net/download.html
 
-With these enviroment variables properly set:
+With these environment variables properly set:
 
   $ set BOOST_ROOT=...
   $ set LUA_PATH=...

doc/GetGitRevisionDescription.cmake

@@ -3,16 +3,16 @@
 # These functions force a re-configure on each git commit so that you can
 # trust the values of the variables in your build system.
 #
-#  get_git_head_revision(<refspecvar> <hashvar> [<additonal arguments to git describe> ...])
+#  get_git_head_revision(<refspecvar> <hashvar> [<additional arguments to git describe> ...])
 #
 # Returns the refspec and sha hash of the current head revision
 #
-#  git_describe(<var> [<additonal arguments to git describe> ...])
+#  git_describe(<var> [<additional arguments to git describe> ...])
 #
 # Returns the results of git describe on the source tree, and adjusting
 # the output so that it tests false if an error occurs.
 #
-#  git_get_exact_tag(<var> [<additonal arguments to git describe> ...])
+#  git_get_exact_tag(<var> [<additional arguments to git describe> ...])
 #
 # Returns the results of git describe --exact-match on the source tree,
 # and adjusting the output so that it tests false if there was no exact

doc/changes.txt

@@ -13,7 +13,7 @@ We have introduced a change that may break current code,
 nothing will break silently however.
 
 The change is that the previous way of writing virtual class
-wrappers was to have it contain an object that refered to
+wrappers was to have it contain an object that referred to
 the actual lua object. This would cause a dependency cycle
 and result in the object never being garbage collected until
 the whole lua state was closed. The new way is to use a newly
@@ -31,7 +31,7 @@ Changes from beta6
   * moved iterators out of the class and removed
     begin/end/raw_begin/raw_end/array_begin/array_end.
     See updated docs for how to use the iterators.
-  * removed array_iterator alltogether
+  * removed array_iterator altogether
   * renamed pushvalue() to push()
   * removed set()
   * replaced the constructor that creates an object from
@@ -111,9 +111,9 @@ policy placeholders
 
 luabind now handles member functions in a more general way.
 The self reference that is passed as first parameter to
-member functions is now refered to using the _1 placeholder
+member functions is now referred to using the _1 placeholder
 (instead of self). This means that the first argument to a
-member function is refered to with _2.
+member function is referred to with _2.
 
 
 additions

doc/docs.rst

@@ -2228,7 +2228,7 @@ pcall_callback function, see ``errfunc`` under the
 For more information on how to retrieve debugging information from lua, see
 `the debug section of the lua manual`_.
 
-The message returned by the ``pcall_callback`` is accessable as the top lua
+The message returned by the ``pcall_callback`` is accessible as the top lua
 value on the stack. For example, if you would like to access it as a luabind
 object, you could do like this::
 
@@ -2309,7 +2309,7 @@ to catch all exceptions and translate them into proper lua errors (by calling
 In Visual Studio, ``catch (...)`` will not only catch C++ exceptions, it will
 also catch structured exceptions, such as segmentation fault. This means that if
 your function, that gets called from luabind, makes an invalid memory
-adressing, you won't notice it. All that will happen is that lua will return
+addressing, you won't notice it. All that will happen is that lua will return
 an error message saying "unknown exception".
 
 To remedy this, you can create your own *exception translator*::
@@ -2582,7 +2582,7 @@ Do I have to register destructors for my classes?
 .. And again, the above is irrelevant to docs. This isn't a general C++ FAQ. But it saves us support questions.
 
 Fatal Error C1063 compiler limit \: compiler stack overflow in VC
-    VC6.5 chokes on warnings, if you are getting alot of warnings from your 
+    VC6.5 chokes on warnings, if you are getting a lot of warnings from your 
     code try suppressing them with a pragma directive, this should solve the 
     problem.
 

src/object_rep.cpp

@@ -211,7 +211,7 @@ namespace luabind { namespace detail
         lua_newtable(L);
 
         // This is used as a tag to determine if a userdata is a luabind
-        // instance. We use a numeric key and a cclosure for fast comparision.
+        // instance. We use a numeric key and a cclosure for fast comparison.
         lua_pushnumber(L, 1);
         lua_pushcclosure(L, get_instance_value, 0);
         lua_rawset(L, -3);