Remove mentions of the obsolete ResourceConfig/AccessConfig.

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

docs/manual/configuring.html

@@ -35,25 +35,21 @@ <H2><a name="main">Main Configuration Files</a></H2>
 
 <td valign="top">
 <strong>Related Directives</strong><br><br>
-<A HREF="mod/core.html#accessconfig">AccessConfig</A><br>
 <A HREF="mod/core.html#ifdefine">&lt;IfDefine&gt;</A><br>
 <a href="mod/core.html#include">Include</a><br>
-<A HREF="mod/core.html#resourceconfig">ResourceConfig</A><br>
 <A HREF="mod/mod_mime.html#typesconfig">TypesConfig</A><br>
 </td></tr></table>
 
 <P>Apache is configured by placing <A HREF="mod/directives.html"
 >directives</A> in plain text configuration files.  The main
 configuration file is usually called <CODE>httpd.conf</CODE>.  The
 location of this file is set at compile-time, but may be overridden
-with the <CODE>-f</CODE> command line flag.  Some sites also have
-<CODE>srm.conf</CODE> and <CODE>access.conf</CODE> files for <A
-HREF="http://www.apache.org/info/three-config-files.html">historical
-reasons</A>.  In addition, other configuration files may be added using
-the <CODE><A HREF="mod/core.html#include">Include</A></CODE>
-directive.  Any directive may be placed in any of these configuration
-files.  Changes to the main configuration files are only recognized by
-Apache when it is started or restarted.</p>
+with the <CODE>-f</CODE> command line flag.  In addition, other
+configuration files may be added using the <CODE><A
+HREF="mod/core.html#include">Include</A></CODE> directive.  Any
+directive may be placed in any of these configuration files.  Changes
+to the main configuration files are only recognized by Apache when it
+is started or restarted.</p>
 
 <P>
 The server also reads a file containing mime document types; the
@@ -193,7 +189,7 @@ <H2><a name="htaccess">.htaccess Files</a></H2>
 <hr>
 
 <H2><a name="logs">Log files</a></H2>
-<!-- This section should be moved to its own file -->
+<!-- XXX: This section should be moved to its own file -->
 <H3>security warning</H3>
 Anyone who can write to the directory where Apache is writing a
 log file can almost certainly gain access to the uid that the server is

docs/manual/configuring.html.en

@@ -35,25 +35,21 @@
 
 <td valign="top">
 <strong>Related Directives</strong><br><br>
-<A HREF="mod/core.html#accessconfig">AccessConfig</A><br>
 <A HREF="mod/core.html#ifdefine">&lt;IfDefine&gt;</A><br>
 <a href="mod/core.html#include">Include</a><br>
-<A HREF="mod/core.html#resourceconfig">ResourceConfig</A><br>
 <A HREF="mod/mod_mime.html#typesconfig">TypesConfig</A><br>
 </td></tr></table>
 
 <P>Apache is configured by placing <A HREF="mod/directives.html"
 >directives</A> in plain text configuration files.  The main
 configuration file is usually called <CODE>httpd.conf</CODE>.  The
 location of this file is set at compile-time, but may be overridden
-with the <CODE>-f</CODE> command line flag.  Some sites also have
-<CODE>srm.conf</CODE> and <CODE>access.conf</CODE> files for <A
-HREF="http://www.apache.org/info/three-config-files.html">historical
-reasons</A>.  In addition, other configuration files may be added using
-the <CODE><A HREF="mod/core.html#include">Include</A></CODE>
-directive.  Any directive may be placed in any of these configuration
-files.  Changes to the main configuration files are only recognized by
-Apache when it is started or restarted.</p>
+with the <CODE>-f</CODE> command line flag.  In addition, other
+configuration files may be added using the <CODE><A
+HREF="mod/core.html#include">Include</A></CODE> directive.  Any
+directive may be placed in any of these configuration files.  Changes
+to the main configuration files are only recognized by Apache when it
+is started or restarted.</p>
 
 <P>
 The server also reads a file containing mime document types; the
@@ -193,7 +189,7 @@ directive in the main configuration files.
 <hr>
 
 <H2><a name="logs">Log files</a></H2>
-<!-- This section should be moved to its own file -->
+<!-- XXX: This section should be moved to its own file -->
 <H3>security warning</H3>
 Anyone who can write to the directory where Apache is writing a
 log file can almost certainly gain access to the uid that the server is