Fix spelling errors. NFCI. Thanks to jsosef for the patch

boost-build.jam

@@ -9,7 +9,7 @@
 # folder. It allows us to choose which Boost Build installation to use for
 # building Boost libraries. Unless explicitly selected using a command-line
 # option, the version included with the Boost library distribution is used (as
-# opposed to any other Boost Build version installed on the user's sytem).
+# opposed to any other Boost Build version installed on the user's system).
 
 BOOST_ROOT = $(.boost-build-file:D) ;
 BOOST_BUILD = [ MATCH --boost-build=(.*) : $(ARGV) ] ;

boostcpp.jam

@@ -390,7 +390,7 @@ class top-level-target : alias-target-class
             local expanded = [ targets.apply-default-build $(property-set)
                 : $(build-type-set) ] ;
 
-            # Filter inappopriate combinations.
+            # Filter inappropriate combinations.
 
             local filtered ;
             local skipped ;
@@ -623,7 +623,7 @@ rule deduce-address-model ( properties * )
     if $(result)
     {
         # Normally, returning composite feature here is equivalent to forcing
-        # consituent properties as well. But we only want to indicate toolset
+        # constituent properties as well. But we only want to indicate toolset
         # deduced default, so also pick whatever address-model is explicitly
         # specified, if any.
         result = <deduced-address-model>$(result) [ property.select <address-model> : $(properties) ] ;

doc/test/HTML4_symbols.qbk

@@ -11,7 +11,7 @@ http://www.boost.org/LICENSE_1_0.txt).
 [/ See http://www.htmlhelp.com/reference/html40/entities/symbols.html]
 [/ All (except 2 angle brackets) show OK on Firefox 2.0]
 
-[/ Also some miscellaneous math charaters added to this list - see the end.]
+[/ Also some miscellaneous math characters added to this list - see the end.]
 
 [/ To use, enclose the template name in square brackets.]
 
@@ -99,7 +99,7 @@ http://www.boost.org/LICENSE_1_0.txt).
 [template notin[]'''∉'''] [/  ? not an element of]
 [template ni[]'''∋'''] [/  ? contains as member]
 [template prod[]'''∏'''] [/  ? n-ary product = product sign]
-[template sum[]'''∑'''] [/  ? n-ary sumation]
+[template sum[]'''∑'''] [/  ? n-ary summation]
 [template minus[]'''−'''] [/  - minus sign]
 [template lowast[]'''∗'''] [/  * asterisk operator]
 [template radic[]'''√'''] [/  v square root = radical sign]

doc/test/gold/document_to_test_formatting/images.html

@@ -27,7 +27,7 @@
 <a name="document_to_test_formatting.images"></a><a class="link" href="images.html" title="Images">Images</a>
 </h2></div></div></div>
 <p>
-      These are tricky enough that they warrent their own section.
+      These are tricky enough that they warrant their own section.
     </p>
 <p>
       Let's start with a PNG file that's set to 120dpi, it should render at a sensible

doc/test/gold/document_to_test_formatting/remez.html

@@ -221,7 +221,7 @@
     </p>
 <p>
       In single point exchange, we move the control point nearest to the largest
-      extrema to the absissa value of the extrema.
+      extrema to the abscissa value of the extrema.
     </p>
 <p>
       In multi-point exchange we swap all the current control points, for the locations
@@ -450,7 +450,7 @@
           and then re-minimise.
         </li>
 <li class="listitem">
-          Keep absissa values small: use a change of variable to keep the abscissa
+          Keep abscissa values small: use a change of variable to keep the abscissa
           over, say [0, b], for some smallish value <span class="emphasis"><em>b</em></span>.
         </li>
 </ul></div>

doc/test/gold/index.html

@@ -137,7 +137,7 @@
       We can count in Greek too: α, β, γ.
     </p>
 <p>
-      Try some superscrips and subscripts: x<sup>2</sup>, x<sub>i</sub><sup>3</sup>, &#945;<sup>2</sup>, &#946;<sup>&#945;</sup>, &#8970;x&#8971;, &#8970;&#945;&#8971;, &#8968;a&#8969;.
+      Try some superscripts and subscripts: x<sup>2</sup>, x<sub>i</sub><sup>3</sup>, &#945;<sup>2</sup>, &#946;<sup>&#945;</sup>, &#8970;x&#8971;, &#8970;&#945;&#8971;, &#8968;a&#8969;.
     </p>
 </div>
 </div>

doc/test/remez.qbk

@@ -142,7 +142,7 @@ The N+2 extrema can then be found using standard function minimisation technique
 We now have a choice: multi-point exchange, or single point exchange.
 
 In single point exchange, we move the control point nearest to the largest extrema to
-the absissa value of the extrema.
+the abscissa value of the extrema.
 
 In multi-point exchange we swap all the current control points, for the locations
 of the extrema.
@@ -317,7 +317,7 @@ retaining the last set of control points at each stage.
 * Try using a smaller interval.  It may also be possible to optimise over
 one (small) interval, rescale the control points over a larger interval,
 and then re-minimise.
-* Keep absissa values small: use a change of variable to keep the abscissa
+* Keep abscissa values small: use a change of variable to keep the abscissa
 over, say \[0, b\], for some smallish value /b/.
 
 [h4 References]

doc/test/test.qbk

@@ -35,7 +35,7 @@ This is some body text.
 
 We can count in Greek too: [alpha], [beta], [gamma].
 
-Try some superscrips and subscripts: x[super 2], x[sub i][super 3], [alpha][super 2], 
+Try some superscripts and subscripts: x[super 2], x[sub i][super 3], [alpha][super 2], 
 [beta][super [alpha]], [floor x], [floor [alpha]], [ceil a].
 
 [endsect]
@@ -592,7 +592,7 @@ ibeta_inva, and ibeta_invb respectively.]]
 
 [section Images]
 
-These are tricky enough that they warrent their own section.
+These are tricky enough that they warrant their own section.
 
 Let's start with a PNG file that's set to 120dpi, it should render at 
 a sensible size in both html and PDF forms.  It should print OK too!

doc/test/test_HTML4_symbols.qbk

@@ -2,7 +2,7 @@
 [/ Examples of using all the Greek and Math symbols defined in HTML4_symbols.qbk]
 [/ See http://www.htmlhelp.com/reference/html40/entities/symbols.html]
 
-[/ Also some miscellaneous math charaters added to this list - see the end.]
+[/ Also some miscellaneous math characters added to this list - see the end.]
 
 [/ To use, enclose the template name in square brackets.]
 

status/explicit-failures-markup.xml

@@ -995,7 +995,7 @@
             <test name="public_function-throwing_body_virtual_branch"/>
             <toolset name="qcc-4.7*"/>
             <note author="Lorenzo Caminiti">
-                This test fails because `std::unchaught_exception` seems to
+                This test fails because `std::uncaught_exception` seems to
                 always return zero on this compiler (even if the authors could
                 not find a direct reference to this possible compiler issue
                 online).
@@ -1677,7 +1677,7 @@
             <toolset name="cw-9.5*"/>
             <note author="J. Garland">
                  Although these tests compile, the execution aborts for
-                 an unknown reason. Note that sometimes the excution is
+                 an unknown reason. Note that sometimes the execution is
                  ok on cw-9_4. This may be fixable if someone
                  can track down the source of the problem.
             </note>
@@ -1942,7 +1942,7 @@
         <mark-unusable>
             <toolset name="msvc-8.0~wm5~stlport5.1"/>
             <note author="Beman Dawes">
-                Due to lack of C library featues, this toolset is not supported.
+                Due to lack of C library features, this toolset is not supported.
             </note>
         </mark-unusable>
         <mark-expected-failures>
@@ -2246,7 +2246,7 @@
     </library>
 
     <!-- functional/forward -->
-    <library name="functional/foward">
+    <library name="functional/forward">
         <mark-unusable>
             <toolset name="msvc-7.0*"/>
             <toolset name="msvc-7.1*"/>
@@ -2359,8 +2359,8 @@
             <toolset name="gcc-4.4~c++0x*"/>
             <toolset name="gcc-4.4~gnu0x*"/>
             <note author="Kohei Takahashi">
-                The compiler doesn't generate defaulted move ctor/assgin thus
-                perform copy construction/assginment. Even though such case,
+                The compiler doesn't generate defaulted move ctor/assign thus
+                perform copy construction/assignment. Even though such case,
                 the `inline` versions don't force generating move ctor/assign
                 to preserve trivial requirements. Since that is not documented
                 behaviour, it might be changed in future release.
@@ -3538,7 +3538,7 @@ for more information.
             <test name="lambda_tests15"/>
             <toolset name="msvc-12.0"/>
             <note author="Kohei Takahsahi">
-                Wrokaround: define BOOST_RESULT_OF_USE_TR1
+                Workaround: define BOOST_RESULT_OF_USE_TR1
             </note>
         </mark-expected-failures>
     </library>
@@ -3694,7 +3694,7 @@ for more information.
             <toolset name="msvc-7.0"/>
             <note author="Robert Ramey" refid="6">
                 msvc 6 compiler failure.  The facility being tested conflicts the the
-                compiler in a fundamental way and cannnot be worked around.
+                compiler in a fundamental way and cannot be worked around.
             </note>
         </mark-expected-failures>
 
@@ -3703,7 +3703,7 @@ for more information.
             <toolset name="msvc-6.5*"/>
             <note author="Robert Ramey" refid="6">
                 msvc 6 compiler failure.  The facility being tested conflicts the the
-                compiler in a fundamental way and cannnot be worked around.
+                compiler in a fundamental way and cannot be worked around.
             </note>
         </mark-expected-failures>
 
@@ -3764,7 +3764,7 @@ for more information.
             <note author="Rene Rivera">
                 The CW compilers have problems with the static construction idiom used to
                 implement the type registration in the Boost.Serialization library. In many
-                cases CW specific work arounds are implemented in the library but this one
+                cases CW specific workarounds are implemented in the library but this one
                 is not immediately solvable. There is a user work around possible, please
                 contact the library developers on the Boost list for information on the
                 work around if needed.
@@ -4668,7 +4668,7 @@ for more information.
             <toolset name="borland-5.8*"/>
             <toolset name="borland-5.9*"/>
             <note author="A.Meredith">
-                This compiler has some problems with name looup / overload resolution.
+                This compiler has some problems with name lookup / overload resolution.
             </note>
         </mark-expected-failures>
         <mark-expected-failures>
@@ -5363,7 +5363,7 @@ for more information.
                 <note author="John Maddock">
                   Reported to Intel as issue 409291, and confirmed
                   as a problem.  Probably this relates to a specific
-                  Linux-Kernal or GLibC version.
+                  Linux-Kernel or GLibC version.
                 </note>
             </mark-failure>
             <mark-failure>
@@ -5680,7 +5680,7 @@ for more information.
             <test name="regex_timer"/>
             <toolset name="msvc-6.5_stlport4"/>
             <note author="John Maddock">
-               Test fails due to unresilved externals from STLport: appears to be
+               Test fails due to unresolved externals from STLport: appears to be
                an STLport bug. </note>
         </mark-expected-failures>
         <mark-expected-failures>
@@ -6083,7 +6083,7 @@ for more information.
                 cleanup is handled by the library implementation. For threads, launched
                 by the native operating system API it is not possible to get this cleanup
                 on every compiler/platform. A warning (error) will be present in this case,
-                which cleary states this fact. It is recommended to start threads only
+                which clearly states this fact. It is recommended to start threads only
                 by means of the Boost.Thread API if you need to avoid the leaks that appear
                 on the end of the thread. If this is not possible the cleanup can be invoked
                 from user code before the process actually ends. For library implementors
@@ -6514,7 +6514,7 @@ This platform doesn't supports Boost.Container.
         <mark-unusable>
             <toolset name="cw-*"/>
             <note author="John Maddock">
-                Metrowerks Codeworrier has partial TR1 support built in
+                Metrowerks Codewarrior has partial TR1 support built in
                 which conflicts with this implementation.  Porting to this
                 compiler is almost certainly possible, but will require some
                 work by someone who has this compiler.
@@ -6758,7 +6758,7 @@ This platform doesn't supports Boost.Container.
             <toolset name="gcc-4*darwin"/>
             <toolset name="darwin*"/>
             <note author="John Maddock">
-               These tests fail on this platform due to a recuring GCC bug.
+               These tests fail on this platform due to a recurring GCC bug.
             </note>
         </mark-expected-failures>