Hey.

In mod/core.html with the documentation for AllowOverride and AllowOverrideList there are IMO a number of issues.


1) Both use the phrase "[...] it needs to know which directives declared in that file can override earlier configuration directives."

Strictly speaking though, this is wrong, as these directives cannot only *override* earlier configuration directives (which kinda implies they'd need to have been set before), but generally *set* them (whether or not they were used outside of the .htaccess).


2) In the Apache 2.4 documentation it probably makes no sense (and is just confusing) to mentioned the defaults of earlier versions, i.e.:
"AllowOverride None (2.3.9 and later), AllowOverride All (2.3.8 and earlier)"


3) While it becomes clear from mod/overrides.html (and one can perhaps blindly assume this behaviour), neither AllowOverride nor AllowOverrideList mention, that they conjunction of both is the effective set of allowed directives.


4) The syntax field of AllowOverrideList contains a probable copy&paste error:
"AllowOverrideList None|directive [directive-type] ..."
should likely read:
"AllowOverrideList None|directive [directive] ..."


5) Neither AllowOverride nor AllowOverrideList mention, that there is the "All"-group of directives (as explained in mod/overrides.html), i.e. directives which are always allowed as soon as the overrides-mechanism (.htaccess) is enabled with at least one directive or group.
I think this is however rather important to know.


Cheers,
Chris.