From: Joshua Slive <slive@apache.org>
Date: Wed, 19 Sep 2001 15:18:16 +0000 (+0000)
Subject: Couple small updates to dso.html
X-Git-Tag: 2.0.26~216
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=65b07afc5d3fd9877f661a833c8301a6da3fc9b5;p=thirdparty%2Fapache%2Fhttpd.git

Couple small updates to dso.html


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91087 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/dso.html b/docs/manual/dso.html
index 3fcadb0b586..2ed4fbbaeae 100644
--- a/docs/manual/dso.html
+++ b/docs/manual/dso.html
@@ -13,7 +13,7 @@
 >
 <!--#include virtual="header.html" -->
 
-<H1>
+<H1 align="center">
 Dynamic Shared Object (DSO) Support
 </H1>
 
@@ -54,18 +54,20 @@ behind their use.</p>
 
 <H2><a name="implementation">Implementation</a></H2>
 
-<P>The DSO support for loading individual Apache modules is based on a module
-named <A HREF="mod/mod_so.html"><CODE>mod_so.c</CODE></A> which must be
-statically compiled into the Apache core. It is the only module besides
-<CODE>core.c</CODE> which cannot be put into a DSO itself.
-Practically all other distributed Apache modules then can
-then be placed into a DSO by individually enabling the DSO build for them via
-<CODE>configure</CODE>'s <CODE>--enable-<i>module</i>=shared</CODE> option 
-(see top-level <CODE>INSTALL</CODE> file).  After a module is compiled into
-a DSO named <CODE>mod_foo.so</CODE> you can use <A
+<P>The DSO support for loading individual Apache modules is based on a
+module named <A HREF="mod/mod_so.html"><CODE>mod_so.c</CODE></A> which
+must be statically compiled into the Apache core. It is the only
+module besides <CODE>core.c</CODE> which cannot be put into a DSO
+itself.  Practically all other distributed Apache modules then can
+then be placed into a DSO by individually enabling the DSO build for
+them via <CODE>configure</CODE>'s
+<CODE>--enable-<i>module</i>=shared</CODE> option as disucussed in the
+<a href="install.html">install documentation</a>.  After a module is
+compiled into a DSO named <CODE>mod_foo.so</CODE> you can use <A
 HREF="mod/mod_so.html"><CODE>mod_so</CODE></A>'s <A
-HREF="mod/mod_so.html#loadmodule"><CODE>LoadModule</CODE></A> command in your
-<CODE>httpd.conf</CODE> file to load this module at server startup or restart.
+HREF="mod/mod_so.html#loadmodule"><CODE>LoadModule</CODE></A> command
+in your <CODE>httpd.conf</CODE> file to load this module at server
+startup or restart.
 
 <P>To simplify this creation of DSO files for Apache modules
 (especially for third-party modules) a new support program named <a
diff --git a/docs/manual/dso.html.en b/docs/manual/dso.html.en
index 3fcadb0b586..2ed4fbbaeae 100644
--- a/docs/manual/dso.html.en
+++ b/docs/manual/dso.html.en
@@ -13,7 +13,7 @@
 >
 <!--#include virtual="header.html" -->
 
-<H1>
+<H1 align="center">
 Dynamic Shared Object (DSO) Support
 </H1>
 
@@ -54,18 +54,20 @@ behind their use.</p>
 
 <H2><a name="implementation">Implementation</a></H2>
 
-<P>The DSO support for loading individual Apache modules is based on a module
-named <A HREF="mod/mod_so.html"><CODE>mod_so.c</CODE></A> which must be
-statically compiled into the Apache core. It is the only module besides
-<CODE>core.c</CODE> which cannot be put into a DSO itself.
-Practically all other distributed Apache modules then can
-then be placed into a DSO by individually enabling the DSO build for them via
-<CODE>configure</CODE>'s <CODE>--enable-<i>module</i>=shared</CODE> option 
-(see top-level <CODE>INSTALL</CODE> file).  After a module is compiled into
-a DSO named <CODE>mod_foo.so</CODE> you can use <A
+<P>The DSO support for loading individual Apache modules is based on a
+module named <A HREF="mod/mod_so.html"><CODE>mod_so.c</CODE></A> which
+must be statically compiled into the Apache core. It is the only
+module besides <CODE>core.c</CODE> which cannot be put into a DSO
+itself.  Practically all other distributed Apache modules then can
+then be placed into a DSO by individually enabling the DSO build for
+them via <CODE>configure</CODE>'s
+<CODE>--enable-<i>module</i>=shared</CODE> option as disucussed in the
+<a href="install.html">install documentation</a>.  After a module is
+compiled into a DSO named <CODE>mod_foo.so</CODE> you can use <A
 HREF="mod/mod_so.html"><CODE>mod_so</CODE></A>'s <A
-HREF="mod/mod_so.html#loadmodule"><CODE>LoadModule</CODE></A> command in your
-<CODE>httpd.conf</CODE> file to load this module at server startup or restart.
+HREF="mod/mod_so.html#loadmodule"><CODE>LoadModule</CODE></A> command
+in your <CODE>httpd.conf</CODE> file to load this module at server
+startup or restart.
 
 <P>To simplify this creation of DSO files for Apache modules
 (especially for third-party modules) a new support program named <a