diff --git a/doc/interoperability-revisited.rst b/doc/interoperability-revisited.rst
index 6754b9c..e75a2c6 100755
--- a/doc/interoperability-revisited.rst
+++ b/doc/interoperability-revisited.rst
@@ -67,7 +67,7 @@ Mutable  m;
 c == m; // ok, dispatched to Constant::equal_to
 m == c; // !! error, dispatched to Mutable::equal_to
 
-Instead the following "slightly" more complicated implementation is neccessary
+Instead the following "slightly" more complicated implementation is necessary
 
 struct Mutable : Facade<Mutable>
 {
@@ -87,7 +87,7 @@ struct Constant : Tag<Constant>
 
 Beside the fact that the code is significantly more complex to understand and to teach there is
 a major design problem lurking here. Note that in both types equal_to is a function template with 
-an unconstrained argument T. This is neccessary so that further types can be made interoperable with
+an unconstrained argument T. This is necessary so that further types can be made interoperable with
 Mutable or Constant. Would Mutable be defined as  
 
 struct Mutable : Facade<Mutable>
@@ -229,4 +229,4 @@ Iterator implementations using iterator_facade look exactly as if they were
 a) Less burden for the user
 
 b) The definition (standardese) of specialized adpters might be easier 
-   (This has to be proved yet)
\ No newline at end of file
+   (This has to be proved yet)
diff --git a/doc/pointee.html b/doc/pointee.html
index 8710f08..6f4f5ca 100755
--- a/doc/pointee.html
+++ b/doc/pointee.html
@@ -63,7 +63,7 @@ determine the appropriate <tt class="literal"><span class="pre">::type</span></t
 <tt class="literal"><span class="pre">Dereferenceable</span></tt>s, but it makes very good guesses (it works
 for all pointers, standard and boost smart pointers, and
 iterators), and when it guesses wrongly, it can be specialized as
-neccessary:</p>
+necessary:</p>
 <pre class="literal-block">
 namespace boost
 {
diff --git a/doc/pointee.rst b/doc/pointee.rst
index 68b9961..9f47692 100755
--- a/doc/pointee.rst
+++ b/doc/pointee.rst
@@ -42,7 +42,7 @@ determine the appropriate ``::type`` reliably for all
 ``Dereferenceable``\ s, but it makes very good guesses (it works
 for all pointers, standard and boost smart pointers, and
 iterators), and when it guesses wrongly, it can be specialized as
-neccessary::
+necessary::
 
   namespace boost
   {
diff --git a/include/boost/iterator/detail/config_def.hpp b/include/boost/iterator/detail/config_def.hpp
index 1c71606..90e2aa7 100644
--- a/include/boost/iterator/detail/config_def.hpp
+++ b/include/boost/iterator/detail/config_def.hpp
@@ -40,7 +40,7 @@
 // end up using a proxy for operator[] when we otherwise shouldn't.
 // Using reference constness gives it an extra hint that it can
 // return the value_type from operator[] directly, but is not
-// strictly neccessary.  Not sure how best to resolve this one.
+// strictly necessary.  Not sure how best to resolve this one.
 
 # define BOOST_ITERATOR_REF_CONSTNESS_KILLS_WRITABILITY 1