Fix misspelled EnableMCMPReceive option

docs/src/main/asciidoc/faq.adoc

@@ -38,7 +38,7 @@ Advertise directive or set explicitly:
 ServerAdvertise Off
 ----
 
-On the worker side, add the addresses and ports of the VirtualHost receiving MCMP (having `EnableMCPMReceive`) to the `proxyList`
+On the worker side, add the addresses and ports of the VirtualHost receiving MCMP (having `EnableMCMPReceive`) to the `proxyList`
 property and set advertise to false, for example:
 
 === JBoss AS 5
@@ -163,7 +163,7 @@ ServerAdvertise On http://localhost:6666
 [error] [client 10.33.144.3] client denied by server configuration: /
 ----
 
-You need to have something like the undermentioned authentication configured in the `EnableMCPMReceive` marked VirtualHost:
+You need to have something like the undermentioned authentication configured in the `EnableMCMPReceive` marked VirtualHost:
 
 [source]
 ----
@@ -200,7 +200,7 @@ This whole magic is in place in order to prevent congestion.
 
 == Keep seeing "HTTP/1.1 501 Method Not Implemented"
 
-One needs to configure EnableMCPMReceive in
+One needs to configure EnableMCMPReceive in
 the VirtualHost where you received the MCMP elements in the Apache httpd configuration.
 Something like in the aforementioned Minimal Example.
 

docs/src/main/asciidoc/native.adoc

@@ -214,17 +214,20 @@ Controls whether a node upon failover is chosen deterministically.
 The Context of a mod_manger directive is VirtualHost except mentioned otherwise. **server config** means that it must be outside a
 VirtualHost configuration. If not an error message will be displayed and httpd will not start.
 
-=== EnableMCPMReceive
+=== EnableMCMPReceive
 
-EnableMCPMReceive – allow the VirtualHost to receive Mod-Cluster Management Protocol (MCMP) messages. You need one
-EnableMCPMReceive in your httpd configuration to allow mod_proxy_cluster to work, put it in the VirtualHost where you
+EnableMCMPReceive – allow the VirtualHost to receive Mod-Cluster Management Protocol (MCMP) messages. You need one
+EnableMCMPReceive in your httpd configuration to allow mod_proxy_cluster to work, put it in the VirtualHost where you
 configure advertise.
 
 This directive was added to address the issue of receiving MCMP on arbitrary VirtualHosts which was problematic
 due to accepting messages on insecure, unintended VirtualHosts.
 
 **Default:** disabled (presence of the directive enables this functionality)
 
+NOTE: This directive deprecates the original EnableMCPMReceive option as it contains a typo. The directive with the correct spelling
+is available in versions higher than 1.3.20.Final.
+
 === MemManagerFile
 
 That is the base name for the names mod_manager will use to store configuration, generate keys for shared memory or lock
@@ -450,7 +453,7 @@ LoadModule watchdog_module      modules/mod_watchdog.so
   </Location>
 
   ServerAdvertise On
-  EnableMCPMReceive
+  EnableMCMPReceive
 
   # Where administrator reads the console from
   <Location /mod_cluster-manager>
@@ -563,7 +566,7 @@ Directory modules now contains all necessary modules:
 C:\Users\%username%\mod_proxy_cluster\native\build (main)
 copy modules\*.so C:\Users\%username%\Apache24\modules\
 'modules/mod_advertise.so' -> 'C:/Users/karm/Apache24/modules/mod_advertise.so'
-'odules/mod_manager.so' -> 'C:/Users/karm/Apache24/modules/mod_manager.so'
+'modules/mod_manager.so' -> 'C:/Users/karm/Apache24/modules/mod_manager.so'
 'modules/mod_proxy_cluster.so' -> 'C:/Users/karm/Apache24/modules/mod_proxy_cluster.so'
 ----
 

docs/src/main/asciidoc/quickstart.adoc

@@ -109,7 +109,7 @@ LoadModule slotmem_shm_module   modules/mod_slotmem_shm.so
      Require ip 127.0.0
     </Location>
 
-    EnableMCPMReceive
+    EnableMCMPReceive
     <Location /mod_cluster_manager>
        SetHandler mod_cluster-manager
        Require ip 127.0.0