aboutsummaryrefslogtreecommitdiff
path: root/lib/Apache
diff options
context:
space:
mode:
authorroot <root@rbsd.ankarstrom.se>2021-04-25 00:00:45 +0000
committerroot <root@rbsd.ankarstrom.se>2021-04-25 00:00:45 +0000
commitf17c54a6e8c837c7de221e717830c1e9df9ce74f (patch)
tree2c553bf8667b4d5f032b3c32c8ad15e31cfd827d /lib/Apache
parent0b3e1490d5b92eee33c524f41570d9502ba719e9 (diff)
downloadApache-Inject-f17c54a6e8c837c7de221e717830c1e9df9ce74f.tar.gz
Clarify documentation
Diffstat (limited to 'lib/Apache')
-rw-r--r--lib/Apache/Inject.pm4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Apache/Inject.pm b/lib/Apache/Inject.pm
index 38aae8e..8de0249 100644
--- a/lib/Apache/Inject.pm
+++ b/lib/Apache/Inject.pm
@@ -82,8 +82,8 @@ The Inject directive serves a much more specific purpose than
server-side includes. It is designed for injecting headers and
footers that belong in the E<lt>bodyE<gt> element, such as headings,
menu bars and copyright notices. While you can technically include
-E<lt>headE<gt> elements in your header file, they will be placed
-in the body of the HTML page and not in the head.
+E<lt>headE<gt> elements in your header file, Apache::Inject will
+place them in the body of the HTML page and not in the head.
The main benefit over server-side includes is that the header and
footer is specified in the server configuration instead of the HTML