From eef73d6a54e94cf61506e99eaa4e7bfa60a5a7da Mon Sep 17 00:00:00 2001
From: Daniel Gruno
@@ -107,7 +107,7 @@ module AP_MODULE_DECLARE_DATA example_module =
This bit of code lets the server know that we have now registered a new module
in the system, and that its name is
example_module
. The name
-of the module is used primarilly for two things:
+of the module is used primarily for two things:
OK
or a HTTP status code does not necessarilly mean
+Returning OK
or a HTTP status code does not necessarily mean
that the request will end. The server may still have other handlers that are
interested in this request, for instance the logging modules which, upon a
successful request, will write down a summary of what was requested and how
@@ -440,7 +440,7 @@ clean up after yourself - pretty neat, huh?
-In our module, we will primarilly be allocating memory for each request, so
+In our module, we will primarily be allocating memory for each request, so
it's appropriate to use the r->pool
reference when creating new objects. A few of the functions for allocating
memory within a pool are:
@@ -837,7 +837,7 @@ for more macros).
configuration in order to invoke a configuration change in our module.
example_set_enabled
: This is a reference to a C function that parses the directive and sets the configuration
accordingly. We will discuss how to make this in the following paragraph.RSRC_CONF
: This tells the server where the directive is permissable. We'll go into details on this value in the
+RSRC_CONF
: This tells the server where the directive is permitted. We'll go into details on this value in the
later chapters, but for now, RSRC_CONF
means that the server will only accept these directives in a server context."Enable or disable...."
: This is simply a brief description of what the directive does.