xforms

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1326945 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/developer/modguide.html.en b/docs/manual/developer/modguide.html.en
index 41a70394a5203fd7e6983a69cb3b9ca55b24ac83..944f1ce9c17e3924a2417abab6b372473492bfd1 100644 (file)
--- a/docs/manual/developer/modguide.html.en
+++ b/docs/manual/developer/modguide.html.en
@@ -60,7 +60,7 @@ First and foremost, you are expected to have a basic knowledge of how the C
 programming language works. In most cases, we will try to be as pedagogical \r
 as possible and link to documents describing the functions used in the \r
 examples, but there are also many cases where it is necessary to either \r
-just assume that "it works" or do some digging youself into what the hows \r
+just assume that "it works" or do some digging yourself into what the hows \r
 and whys of various function calls. \r
 </p>\r
 <p>\r
@@ -107,7 +107,7 @@ module AP_MODULE_DECLARE_DATA   example_module <code style="color:#806030; ">=</
 \r
 This bit of code lets the server know that we have now registered a new module \r
 in the system, and that its name is <code>example_module</code>. The name \r
-of the module is used primarilly for two things:<br />\r
+of the module is used primarily for two things:<br />\r
 <ul>\r
 <li>Letting the server know how to load the module using the LoadModule</li>\r
 <li>Setting up a namespace for the module to use in configurations</li>\r
@@ -360,7 +360,7 @@ status code, for example:
 \r
 \r
 \r
-Returning <code>OK</code> or a HTTP status code does not necessarilly mean \r
+Returning <code>OK</code> or a HTTP status code does not necessarily mean \r
 that the request will end. The server may still have other handlers that are \r
 interested in this request, for instance the logging modules which, upon a \r
 successful request, will write down a summary of what was requested and how \r
@@ -440,7 +440,7 @@ clean up after yourself - pretty neat, huh?
 </p>\r
 \r
 <p>\r
-In our module, we will primarilly be allocating memory for each request, so \r
+In our module, we will primarily be allocating memory for each request, so \r
 it's appropriate to use the <code style="color:#008833">r-&gt;pool</code> \r
 reference when creating new objects. A few of the functions for allocating \r
 memory within a pool are:\r
@@ -837,7 +837,7 @@ for more macros).</li>
 configuration in order to invoke a configuration change in our module.</li>\r
 <li><code>example_set_enabled</code>: This is a reference to a C function that parses the directive and sets the configuration \r
 accordingly. We will discuss how to make this in the following paragraph.</li>\r
-<li><code>RSRC_CONF</code>: This tells the server where the directive is permissable. We'll go into details on this value in the \r
+<li><code>RSRC_CONF</code>: This tells the server where the directive is permitted. We'll go into details on this value in the \r
 later chapters, but for now, <code>RSRC_CONF</code> means that the server will only accept these directives in a server context.</li>\r
 <li><code>"Enable or disable...."</code>: This is simply a brief description of what the directive does.</li>\r
 </ol>\r