From 6c50f384a604fae24502e55371fb52decf456624 Mon Sep 17 00:00:00 2001 From: Daniel Gruno Date: Sat, 20 Apr 2013 10:57:40 +0000 Subject: [PATCH] typo fixes git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1470152 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/developer/modguide.xml | 6 +++--- 1 file 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

The most essential part of any request is the request record . In a call to a handler function, this is represented by the request_rec* structure passed along with every call that is made. -This struct, typically just refered to as r in modules, +This struct, typically just referred to as r in modules, contains all the information you need for your module to fully process any HTTP request and respond accordingly.

Some key elements of the request_rec structure are: @@ -709,7 +709,7 @@ static int example_handler(request_rec *r)

-This version in its entirity can be found here: +This version in its entirety can be found here: mod_example_2.c.

@@ -892,7 +892,7 @@ set them.)
The directive handler function

-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 -- 2.40.0