profile_mode.xml: Minor updates and fixes.

2010-02-22  François Dumont  <francois.cppdevs@free.fr>

       * doc/xml/manual/profile_mode.xml: Minor updates and fixes.
       * doc/xml/manual/debug_mode.xml: Likewise.
       * doc/xml/manual/test.xml: Likewise.

From-SVN: r156975

4 files changed, 15 insertions, 9 deletions

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index d60096a..f6448c1 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,9 @@
+2010-02-22  François Dumont  <francois.cppdevs@free.fr>
+
+       * doc/xml/manual/profile_mode.xml: Minor updates and fixes.
+       * doc/xml/manual/debug_mode.xml: Likewise.
+       * doc/xml/manual/test.xml: Likewise.
+
 2010-02-22  Paolo Carlini  <paolo.carlini@oracle.com>
 
 	* include/tr1_impl/complex (arg): Use std::signbit only when
diff --git a/libstdc++-v3/doc/xml/manual/debug_mode.xml b/libstdc++-v3/doc/xml/manual/debug_mode.xml
index f1610c3..32b87a1 100644
--- a/libstdc++-v3/doc/xml/manual/debug_mode.xml
+++ b/libstdc++-v3/doc/xml/manual/debug_mode.xml
@@ -629,7 +629,7 @@ namespace std
 </programlisting>
   
 <para>In debug mode we include the release-mode container (which is now
-defined in in the namespace <code>__norm</code>) and also the
+defined in the namespace <code>__norm</code>) and also the
 debug-mode container. The debug-mode container is defined within the
 namespace <code>__debug</code>, which is associated with namespace
 <code>std</code> via the C++0x namespace association language feature.  This
@@ -672,7 +672,7 @@ namespace std
     debug-mode components</title>
 
 <para>Because each component has a distinct and separate release and
-debug implementation, there are are no issues with link-time
+debug implementation, there is no issue with link-time
 coexistence: the separate namespaces result in different mangled
 names, and thus unique linkage.</para>
 
@@ -799,7 +799,7 @@ test02()
       enticing option, because it would eliminate the need for
       the <code>link_name</code> extension by aliasing the
       templates. However, there is no true template aliasing mechanism
-      is C++, because both <code>using</code> directives and using
+      in C++, because both <code>using</code> directives and using
       declarations disallow specialization. This method fails
       the <emphasis>correctness</emphasis> criteria.</para></listitem>
 
diff --git a/libstdc++-v3/doc/xml/manual/profile_mode.xml b/libstdc++-v3/doc/xml/manual/profile_mode.xml
index 5396e15..2dfeb62 100644
--- a/libstdc++-v3/doc/xml/manual/profile_mode.xml
+++ b/libstdc++-v3/doc/xml/manual/profile_mode.xml
@@ -128,7 +128,7 @@ vector-size: improvement = 3: call stack = 0x804842c ...
   The warning message.  For some warnings, this is static text, e.g.,
   "change vector to list".  For other warnings, such as the one above,
   the message contains numeric advice, e.g., the suggested initial size
-  of the hashtable.
+  of the vector.
   </para>
   </listitem>
   </itemizedlist>
@@ -199,7 +199,7 @@ vector-size: improvement = 3: call stack = 0x804842c ...
    Make the library not use threads.  If thread local storage (TLS) is not 
    available, you will get a preprocessor error asking you to set
    -D_GLIBCXX_PROFILE_NO_THREADS if your program is single-threaded.
-   Multithreded execution without TLS is not supported.
+   Multithreaded execution without TLS is not supported.
    (Environment variable not supported.)
    </para></listitem>
   <listitem><para>
@@ -536,7 +536,7 @@ it helps the user focus on the key problems and ignore the uninteresting ones.
  xreflabel="Using the Standard Library in the Runtime Library">
 <title>Using the Standard Library in the Instrumentation Implementation</title>
   <para>
-  As much as we would like to avoid uses of stdlibc++ within our 
+  As much as we would like to avoid uses of libstdc++ within our 
   instrumentation library, containers such as unordered_map are very 
   appealing.  We plan to use them as long as they are named properly 
   to avoid ambiguity.
@@ -551,7 +551,7 @@ it helps the user focus on the key problems and ignore the uninteresting ones.
   User applications/libraries can provide malloc hooks.
   When the implementation of the malloc hooks uses stdlibc++, there can
   be an infinite cycle between the profile mode instrumentation and the
-  the malloc hook code.
+  malloc hook code.
   </para>
   <para>
   We protect against reentrance to the profile mode instrumentation code,
diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml
index 56f6c12..6c0f266 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -837,7 +837,7 @@ only default variables.
        </para>
 
        <para>
-	 Random code paths can be constructed using the the basic test
+	 Random code paths can be constructed using the basic test
 	 sequences and instrumentation as above, only combined in a
 	 random or pseudo-random way.
        </para>
@@ -891,7 +891,7 @@ only default variables.
 	 Which has several tests for container member functions,
 Includes control and test container objects. Configuration includes
 random seed, iterations, number of distinct values, and the
-probability that and exception will be thrown. Assumes instantiating
+probability that an exception will be thrown. Assumes instantiating
 container uses an extension
 allocator, <classname>__gnu_cxx::throw_allocator_random</classname>,
 as the allocator type.