From 2f95ee89dfc9a09ec55ce48e16b78f0b391e439c Mon Sep 17 00:00:00 2001
From: Beman Dawes <bdawes@acm.org>
Date: Wed, 26 Nov 2003 18:11:45 +0000
Subject: [PATCH] fix broken link

[SVN r20964]
---
 config.htm | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/config.htm b/config.htm
index 3e3f9b33..f41d9951 100644
--- a/config.htm
+++ b/config.htm
@@ -96,7 +96,7 @@ export LDFLAGS="-DAportable"
 export LIBS="-lpthread"
 ./configure</pre>
       <p>However you run the configure script, when it finishes you will find a new 
-         header - user.hpp - located in the <a href="user.hpp">&lt;boost-root&gt;/libs/config/</a>
+         header - user.hpp - located in the &lt;boost-root/libs/config/&gt;
          directory. <b><i>Note that configure does not install this header into your boost 
                include path by default.</i></b> This header contains all the options 
          generated by the configure script, plus a header-section that contains the user 
@@ -965,8 +965,7 @@ void g() { return f(); }</pre>
                incorrectly outputs <tt>"2 2 double double "</tt> on VC++ 6. These macros, to 
                be used in the function parameter list, fix the problem without effects on the 
                calling syntax. For instance, in the case above write:
-               <pre>
-  template &lt;int n&gt;
+               <pre>  template &lt;int n&gt;
   void f(BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int, n)) { ... }
 
   template &lt;typename T&gt;
@@ -1117,8 +1116,7 @@ void g() { return f(); }</pre>
          declared in your library, in order to avoid sprinkling #pragma's all over the 
          boost headers, there are some prefix and suffix headers that do the job, 
          typical usage would be:</P>
-      <PRE>
-#ifndef MY_INCLUDE_GUARD
+      <PRE>#ifndef MY_INCLUDE_GUARD
 #define MY_INCLUDE_GUARD
 
 // all includes go here:
@@ -1397,4 +1395,4 @@ int test()
       <p>&nbsp;</p>
       <p>&nbsp;</p>
    </body>
-</html>
+</html>
\ No newline at end of file