[multiple changes]

2002-09-13  Andy Felt  <afelt@uwsp.edu>

	* docs/html/17_intro/howto.html:  Update link.

2002-09-13  Phil Edwards  <pme@gcc.gnu.org>

	* docs/doxygen/run_doxygen:  Massage man page for Iterator_types.3.
	* docs/html/faq/index.html:  Whitespace fixes.

From-SVN: r57125

4 files changed, 29 insertions, 19 deletions

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index cd6f8db..6bb38f0 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,12 @@
+2002-09-13  Andy Felt  <afelt@uwsp.edu>
+
+	* docs/html/17_intro/howto.html:  Update link.
+
+2002-09-13  Phil Edwards  <pme@gcc.gnu.org>
+
+	* docs/doxygen/run_doxygen:  Massage man page for Iterator_types.3.
+	* docs/html/faq/index.html:  Whitespace fixes.
+
 2002-09-12  Benjamin Kosnik  <bkoz@redhat.com>
 
 	* libmath/Makefile.am (LIBTOOL): Use --tag CC always for this
diff --git a/libstdc++-v3/docs/doxygen/run_doxygen b/libstdc++-v3/docs/doxygen/run_doxygen
index df7d838..d8ca2a9 100644
--- a/libstdc++-v3/docs/doxygen/run_doxygen
+++ b/libstdc++-v3/docs/doxygen/run_doxygen
@@ -219,7 +219,8 @@ rm stdheader
 # implementations of man(1), e.g., Linux's.  We need to have another top-level
 # *roff tag to /stop/ the .SH NAME entry.
 #problematic=`egrep --files-without-match '^\.SH SYNOPSIS' [A-Z]*.3`
-problematic='Containers.3 Sequences.3 Assoc_containers.3 Allocators.3'
+problematic='Containers.3 Sequences.3 Assoc_containers.3 Allocators.3
+             Iterator_types.3'
 for f in $problematic; do
     sed '/^\.SH NAME/{
 n
diff --git a/libstdc++-v3/docs/html/17_intro/howto.html b/libstdc++-v3/docs/html/17_intro/howto.html
index c3b82f5..a8cf397 100644
--- a/libstdc++-v3/docs/html/17_intro/howto.html
+++ b/libstdc++-v3/docs/html/17_intro/howto.html
@@ -158,7 +158,7 @@
    <p>For those of you new to ISO C++98, no, that isn't a typo, the headers
       really have new names.  Marshall Cline's C++ FAQ Lite has a good
       explanation in
-<a href="http://www.cerfnet.com/~mpcline/On-Line-C++-FAQ/coding-standards.html#[25.4]">item [25.4]</a>.
+<a href="http://www.parashift.com/c++-faq-lite/coding-standards.html#faq-26.4">item [26.4]</a>.
    </p>
    <p>Return <a href="#top">to top of page</a> or
       <a href="../faq/index.html">to the FAQ</a>.
diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html
index 7494334..6d42ebc 100644
--- a/libstdc++-v3/docs/html/faq/index.html
+++ b/libstdc++-v3/docs/html/faq/index.html
@@ -166,8 +166,8 @@
       <p>The libstdc++ project is contributed to by several developers
          all over the world, in the same way as GCC or Linux.
          Benjamin Kosnik, Gabriel Dos Reis, Phil Edwards, Ulrich Drepper, 
-	 Loren James Rittle, and Paolo Carlini are the lead maintainers of 
-	 the CVS archive.
+         Loren James Rittle, and Paolo Carlini are the lead maintainers of 
+         the CVS archive.
       </p>
       <p>Development and discussion is held on the libstdc++ mailing
          list.  Subscribing to the list, or searching the list
@@ -642,8 +642,8 @@ New:
       </p>
       <p><a name="4_4_iostreamclear"><strong>reopening a stream fails</strong>
          </a> Did I just say that -Weffc++ was our biggest false-bug report?
-	 I lied.  (It used to be.)  Today it seems to be reports that after
-	 executing a sequence like
+         I lied.  (It used to be.)  Today it seems to be reports that after
+         executing a sequence like
       </p>
       <pre>
     #include &lt;fstream&gt;
@@ -715,23 +715,23 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
          requires a separate patch for libstdc++-v3.
       </p>
       <p><a name="4_4_checks"><strong>concept checks</strong></a>
-	 If you see compilation errors containing messages about
-	 <code> <em>foo</em>Concept </code>and a<code> constraints </code>
-	 member function, then most likely you have violated one of the
-	 requirements for types used during instantiation of template
-	 containers and functions.  For example, EqualityComparableConcept
-	 appears if your types must be comparable with == and you have not
-	 provided this capability (a typo, or wrong visibility, or you
-	 just plain forgot, etc).
+         If you see compilation errors containing messages about
+         <code> <em>foo</em>Concept </code>and a<code> constraints </code>
+         member function, then most likely you have violated one of the
+         requirements for types used during instantiation of template
+         containers and functions.  For example, EqualityComparableConcept
+         appears if your types must be comparable with == and you have not
+         provided this capability (a typo, or wrong visibility, or you
+         just plain forgot, etc).
       </p>
       <p>More information, including how to optionally enable/disable the
-	 checks, is available
-	 <a href="../19_diagnostics/howto.html#3">here</a>.
+         checks, is available
+         <a href="../19_diagnostics/howto.html#3">here</a>.
       </p>
       <p><a name="4_4_dlsym"><strong>dlopen/dlsym</strong></a>
-	 If you are using the C++ library across dynamically-loaded
-	 objects, make certain that you are passing the correct options
-	 when compiling and linking:
+         If you are using the C++ library across dynamically-loaded
+         objects, make certain that you are passing the correct options
+         when compiling and linking:
       </p>
       <pre>
     // compile the library components