Corrected hyperlinks

1 files changed, 8 insertions, 8 deletions

diff --git a/ACE/ACE-INSTALL.html b/ACE/ACE-INSTALL.html
index 62e2da4ea22..b4b2ed4e9f8 100644
--- a/ACE/ACE-INSTALL.html
+++ b/ACE/ACE-INSTALL.html
@@ -17,7 +17,7 @@ it has been ported to.  Please consult the <a href="NEWS">NEWS</a> and
 <a href="ChangeLog">ChangeLog</a> files to see whether any recent changes
 to the release will affect your code.  In addition, you should check
 out our <a
-href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-development-process.html">development
+href="docs/ACE-development-process.html">development
 process</a>.  As you start working with ACE, we suggest you get copies
 of the <a
 href="http://www.cs.wustl.edu/%7Eschmidt/ACE/book1/">C++NPv1</a>, <a
@@ -25,12 +25,12 @@ href="http://www.cs.wustl.edu/%7Eschmidt/ACE/book2/">C++NPv2</a>, and
 <a href="http://www.riverace.com/acebooks/">APG</a> books to help
 guide you after you've built and installed ACE.  You should also
 consult the <a
-href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-FMM.html">ACE
+href="docs/ACE-FMM.html">ACE
 Frequently Made Mistakes page</a>.  If you encounter any problems or
 would like to request an enhancement, then use our <a
-href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/usage-bugzilla.html">bug
+href="docs/usage-bugzilla.html">bug
 tracking system</a> to submit a report in accordance with our <a
-href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-bug-process.html">bug
+href="docs/ACE-bug-process.html">bug
 report process</a>.<p>
 
 </p><h2>Document Index</h2>
@@ -65,7 +65,7 @@ The <a href="http://www.dre.vanderbilt.edu/">DOC group</a>,
 user community have all contributed ports to make ACE the successful
 and far-reaching toolkit it is today.  Any UNIX/POSIX/Windows
 variation is probably an easy target platform for ACE.  If you have
-<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-porting.html">porting questions</a> or have a problem
+<a href="docs/ACE-porting.html">porting questions</a> or have a problem
 compiling the ACE source distribution, please contact one of the
 commercial support companies, or send a copy of the
 <a href="PROBLEM-REPORT-FORM">PROBLEM-REPORT-FORM</a>, located in the
@@ -98,7 +98,7 @@ to provide build results. Members of the ACE community that maintain ACE on
 platforms not maintained by the DOC group, Riverace, OCI, or Remedy IT are
 encouraged to provide build and regression test results for the scoreboard
 to ensure that all in-use platforms are represented.
-See the <a href="https://svn.dre.vanderbilt.edu/viewvc/ACE_autobuild/trunk/README?revision=HEAD" target="_blank">autobuild README</a> for more information about
+See the <a href="https://svn.dre.vanderbilt.edu/viewvc/autobuild/trunk/README?revision=HEAD" target="_blank">autobuild README</a> for more information about
 how to set up a build; contact one of the above groups to inquire about how
 to get your build results recorded on the scoreboard.</p>
 <p>Because older
@@ -213,7 +213,7 @@ href="http://www.cs.wustl.edu/%7Eschmidt/resume-grants.html">funded
 by</a>) advanced R&amp;D projects. The group continues to be
 intimately involved in ACE+TAO development and maintenance, but with
 revised priorities for maintenance. The <a
-href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-bug-process.html">bug
+href="docs/ACE-bug-process.html">bug
 fixing policies</a> followed by the DOC group are designed to strike a
 balance between their many <a
 href="http://www.cs.wustl.edu/%7Eschmidt/research.html">research
@@ -1488,7 +1488,7 @@ Using the Cygnus tools, this approach works:
   </p></li><li>Set up your
     <code>ACE_wrappers/include/makeinclude/platform_macros.GNU</code>
     as usual for VxWorks.  See
-    <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_vxworks5.5.x.GNU">the
+    <a href="include/makeinclude/platform_vxworks5.5.x.GNU">the
     g++/VxWorks platform file</a> for more information.<p>
   </p></li><li>Create an <code>ACE_wrappers/ace/config.h</code> file that looks
     something like the following.