summaryrefslogtreecommitdiffstats
path: root/docs/manual/developer
diff options
context:
space:
mode:
authorDaniel Gruno <humbedooh@apache.org>2013-04-20 12:57:40 +0200
committerDaniel Gruno <humbedooh@apache.org>2013-04-20 12:57:40 +0200
commit6c50f384a604fae24502e55371fb52decf456624 (patch)
tree58bb2033272856235e66b6f22b9ece008b6aa0fa /docs/manual/developer
parentscrap r:started from the list of functions, as it's just a variable. (diff)
downloadapache2-6c50f384a604fae24502e55371fb52decf456624.tar.xz
apache2-6c50f384a604fae24502e55371fb52decf456624.zip
typo fixes
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1470152 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/developer')
-rw-r--r--docs/manual/developer/modguide.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/manual/developer/modguide.xml b/docs/manual/developer/modguide.xml
index 346c4367cb..01e8e1f80a 100644
--- a/docs/manual/developer/modguide.xml
+++ b/docs/manual/developer/modguide.xml
@@ -304,7 +304,7 @@ looks like
<p>The most essential part of any request is the <em>request record
</em>. In a call to a handler function, this is represented by the <code>
request_rec* </code> structure passed along with every call that is made.
-This struct, typically just refered to as <code>r</code> in modules,
+This struct, typically just referred to as <code>r</code> in modules,
contains all the information you need for your module to fully process any
HTTP request and respond accordingly.</p> <p>Some key elements of the <code>
request_rec </code> structure are:
@@ -709,7 +709,7 @@ static int example_handler(request_rec *r)
<!-- END EXAMPLE CODE -->
<p>
-This version in its entirity can be found here:
+This version in its entirety can be found here:
<a href="http://people.apache.org/~humbedooh/mods/examples/mod_example_2.c">mod_example_2.c</a>.
</p>
</section>
@@ -892,7 +892,7 @@ set them.</em>)
</section>
<section id="directive_handler"><title>The directive handler function</title>
<p>
-Now that we've told the server to expect some directives for our module, it's
+Now that we have told the server to expect some directives for our module, it's
time to make a few functions for handling these. What the server reads in the
configuration file(s) is text, and so naturally, what it passes along to
our directive handler is one or more strings, that we ourselves need to