httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From humbed...@apache.org
Subject svn commit: r1324681 - in /httpd/httpd/trunk/docs/manual/developer: modguide.html.en modguide.xml
Date Wed, 11 Apr 2012 10:02:46 GMT
Author: humbedooh
Date: Wed Apr 11 10:02:46 2012
New Revision: 1324681

URL: http://svn.apache.org/viewvc?rev=1324681&view=rev
Log:
Fix some typos

Modified:
    httpd/httpd/trunk/docs/manual/developer/modguide.html.en
    httpd/httpd/trunk/docs/manual/developer/modguide.xml

Modified: httpd/httpd/trunk/docs/manual/developer/modguide.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/developer/modguide.html.en?rev=1324681&r1=1324680&r2=1324681&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/developer/modguide.html.en (original)
+++ httpd/httpd/trunk/docs/manual/developer/modguide.html.en Wed Apr 11 10:02:46 2012
@@ -1152,7 +1152,7 @@ the directive inside <Directory> a
 
 <h3><a name="context_pool" id="context_pool">Using Apache to allocate configuration
slots</a></h3>
 <p> A much smarter way to manage your configurations is by letting Apache 
-help you create them. To do so, we must first start off by chancing our 
+help you create them. To do so, we must first start off by changing our 
 <em>name tag</em> to let Apache know, that it should assist us in creating 
 and managing our configurations. Since we have chosen the per-directory 
 (or per-location) context for our module configurations, we'll add a 
@@ -1260,7 +1260,7 @@ two configurations and decide how they a
 
 <h3><a name="context_which" id="context_which">Trying out our new context aware
configurations</a></h3>
 <p>
-Now, let's try putting it all together to create a new module that it 
+Now, let's try putting it all together to create a new module that is 
 context aware. First off, we'll create a configuration that lets us test 
 how the module works:
 <div class="example"><pre>

Modified: httpd/httpd/trunk/docs/manual/developer/modguide.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/developer/modguide.xml?rev=1324681&r1=1324680&r2=1324681&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/developer/modguide.xml (original)
+++ httpd/httpd/trunk/docs/manual/developer/modguide.xml Wed Apr 11 10:02:46 2012
@@ -1151,7 +1151,7 @@ the directive inside &lt;Directory&gt; a
 
 <section id="context_pool"><title>Using Apache to allocate configuration slots</title>
 <p> A much smarter way to manage your configurations is by letting Apache 
-help you create them. To do so, we must first start off by chancing our 
+help you create them. To do so, we must first start off by changing our 
 <em>name tag</em> to let Apache know, that it should assist us in creating 
 and managing our configurations. Since we have chosen the per-directory 
 (or per-location) context for our module configurations, we'll add a 
@@ -1259,7 +1259,7 @@ two configurations and decide how they a
 
 <section id="context_which"><title>Trying out our new context aware configurations</title>
 <p>
-Now, let's try putting it all together to create a new module that it 
+Now, let's try putting it all together to create a new module that is 
 context aware. First off, we'll create a configuration that lets us test 
 how the module works:
 <example><pre>



Mime
View raw message