The module name changes will probably hit people in

run-time configuration at least as much as in
compile-time, so mention it there as well.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@349744 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/upgrading.xml b/docs/manual/upgrading.xml
index 2f12bcf6b7dfe4a942a3667cf57bb858b5dd3c4f..0afdf47c19d4db971aec3bf53882a386af336926 100644 (file)
--- a/docs/manual/upgrading.xml
+++ b/docs/manual/upgrading.xml
@@ -71,7 +71,12 @@
     <p>Your existing version 2.0 config files and startup scripts can
       usually be used unchanged in version 2.2.  Some small
       adjustments may be necessary for particular configurations as
-      discussed below.  If you choose to use the new default
+      discussed below.  In addition, if you dynamically load the
+      standard modules using the <directive
+      module="mod_so">LoadModule</directive> directive, then you will
+      need to account for the module name changes mentioned above.</p>
+
+    <p>If you choose to use the new default
       configuration file for version 2.2, you will find that it has
       been greatly simplified by removing all but the most essential
       configuration settings.  A set of example configuration settings