allocator.xml: Minor updates and fixes.

2010-01-26  François Dumont  <francois.cppdevs@free.fr>

	* doc/xml/manual/allocator.xml: Minor updates and fixes.
	* doc/xml/manual/containers.xml: Likewise.
	* doc/xml/manual/using.xml: Likewise.
	* doc/xml/manual/locale.xml: Likewise.
	* doc/xml/manual/appendix_contributing.xml: Likewise.

From-SVN: r156258

libstdc++-v3/ChangeLog

+2010-01-26  François Dumont  <francois.cppdevs@free.fr>
+
+	* doc/xml/manual/allocator.xml: Minor updates and fixes.
+	* doc/xml/manual/containers.xml: Likewise.
+	* doc/xml/manual/using.xml: Likewise.
+	* doc/xml/manual/locale.xml: Likewise.
+	* doc/xml/manual/appendix_contributing.xml: Likewise.
+
 2010-01-26  Daniel Frey  <d.frey@gmx.de>
 
 	* include/std/functional: Use enable_if instead of __enable_if
@@ -35,7 +43,7 @@
 
 2010-01-21  Jonathan Wakely  <jwakely.gcc@gmail.com>
 
-        PR libstdc++/42201
+	PR libstdc++/42201
 	* include/std/future: Update to latest WP.
 	* src/functexcept.cc (__throw_future_error): Use make_error_code.
 	* testsuite/30_threads/async/any.cc: New.
@@ -70,7 +78,7 @@
 	* testsuite/30_threads/unique_future/cons/copy_neg.cc: Adjust.
 	* testsuite/30_threads/unique_future/cons/move.cc: Adjust.
 	* testsuite/30_threads/unique_future/requirements/
-        explicit_instantiation.cc: Adjust.
+	explicit_instantiation.cc: Adjust.
 	* testsuite/30_threads/unique_future/members/is_ready.cc: Remove.
 	* testsuite/30_threads/unique_future/members/has_value.cc: Remove.
 	* testsuite/30_threads/unique_future/members/has_exception.cc: Remove.

libstdc++-v3/doc/xml/manual/allocator.xml

@@ -81,7 +81,7 @@
    </itemizedlist>
 
    <para> 
-     Complete details cam be found in the C++ standard, look in
+     Complete details can be found in the C++ standard, look in
      <constant>[20.4 Memory]</constant>.
    </para>
 
@@ -146,7 +146,7 @@
 
    <para>
      The only allocator interface that
-     is support is the standard C++ interface. As such, all STL
+     is supported is the standard C++ interface. As such, all STL
      containers have been adjusted, and all external allocators have
      been modified to support this change.   
    </para>
@@ -202,7 +202,7 @@
        </para>
        <para>
        This test shows the ability of the allocator to reclaim memory
-     on a pre-thread basis, as well as measuring thread contention
+     on a per-thread basis, as well as measuring thread contention
      for memory resources. 
      Test source 
     <ulink url="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert_erase/associative.cc?view=markup">here</ulink>.
@@ -447,8 +447,8 @@
    <para>The <varname>thr</varname> boolean determines whether the
    pool should be manipulated atomically or not.  When
    <varname>thr</varname> = <constant>true</constant>, the allocator
-   is is thread-safe, while <varname>thr</varname> =
-   <constant>false</constant>, and is slightly faster but unsafe for
+   is thread-safe, while <varname>thr</varname> =
+   <constant>false</constant>, is slightly faster but unsafe for
    multiple threads.
    </para>
 

libstdc++-v3/doc/xml/manual/appendix_contributing.xml

@@ -172,7 +172,7 @@
       <listitem>
 	<para> 
 	  A ChangeLog entry as plain text; see the various
-	  ChangeLog files for format and content. If using you are
+	  ChangeLog files for format and content. If you are
 	  using emacs as your editor, simply position the insertion
 	  point at the beginning of your change and hit CX-4a to bring
 	  up the appropriate ChangeLog entry. See--magic! Similar

libstdc++-v3/doc/xml/manual/containers.xml

@@ -170,7 +170,7 @@
 	  <code>end()</code>, then the item being inserted should have
 	  a key greater than all the other keys in the container.  The
 	  item will be inserted at the end of the container, becoming
-	  the new entry at <code>end()</code>.  
+	  the new entry before <code>end()</code>.  
       </para>
       </listitem>
       <listitem>
@@ -286,7 +286,7 @@
    </para>
    <para>
      The problem is that <code>vector&lt;bool&gt;</code> doesn't
-     behave like a normal vector anymore.  There have been recent
+     behave like a normal vector anymore.  There have been
      journal articles which discuss the problems (the ones by Herb
      Sutter in the May and July/August 1999 issues of C++ Report cover
      it well).  Future revisions of the ISO C++ Standard will change

libstdc++-v3/doc/xml/manual/locale.xml

@@ -38,8 +38,8 @@ class facet
 
 <para>
 Facets actually implement locale functionality. For instance, a facet
-called numpunct is the data objects that can be used to query for the
-thousands separator is in the German locale.
+called numpunct is the data object that can be used to query for the
+thousands separator in the locale.
 </para>
 
 <para>

libstdc++-v3/doc/xml/manual/using.xml

@@ -655,7 +655,7 @@ same translation unit:
 	(<math.h> in this case), the symbols will be available
 	in the global namespace and perhaps in
 	namespace <code>std::</code> (but this is no longer a firm
-	requirement.) One the other hand, including the C++-style
+	requirement.) On the other hand, including the C++-style
 	header (&lt;cmath&gt;) guarantees that the entities will be
 	found in namespace std and perhaps in the global namespace.
       </para>
@@ -808,7 +808,7 @@ and <code>__gnu_pbds</code>.
 std::string;</code>) This approach works well for individual source files, but
 should not be used in a global context, like header files.
 	  </para></listitem> <listitem><para>use a <emphasis>fully
-qualified name</emphasis>for each library symbol
+qualified name</emphasis> for each library symbol
 (i.e. <code>std::string</code>, <code>std::cout</code>) Always can be
 used, and usually enhanced, by strategic use of typedefs. (In the
 cases where the qualified verbiage becomes unwieldy.)