Permalink
Browse files

aspelled modules

git-svn-id: svn://cherokee-project.com/cherokee/trunk@4525 5dc97367-97f1-0310-9951-d761b3857238
  • Loading branch information...
1 parent 9949bff commit 3c112e239a1af2e1aed22d0e2dfc0535596c72cf @skinkie skinkie committed Mar 19, 2010
View
@@ -22,7 +22,7 @@
- link:modules_validators_plain.html[Plain]: Plain file mechanism.
- link:modules_validators_htpasswd.html[htpasswd]: htpasswd mechanism.
- link:modules_validators_htdigest.html[htdigest]: htdigest mechanism.
- - link:modules_validators_ldap.html[LDAP]: Lightweight Directory Acces Protocol mechanism.
+ - link:modules_validators_ldap.html[LDAP]: Lightweight Directory Access Protocol mechanism.
- link:modules_validators_mysql.html[MySQL]: Database mechanism.
- link:modules_validators_pam.html[PAM]: Pluggable Authentication Module mechanism.
- link:modules_validators_authlist.html[Fixed list]: Fixed authentication list.
View
@@ -6,7 +6,7 @@ Modules: Encoders
Encoders are Cherokee modules that can be used as filters. The most
common usage is to compress information allowing you to save
bandwidth. You should do that whenever you can since hardware is
-mostly unexpensive while bandwidth is not. Besides, the performance
+mostly inexpensive while bandwidth is not. Besides, the performance
penalization suffered due to the compression process is trivial, and
if the content is cached you will only suffer it once.
@@ -97,10 +97,10 @@ This info will be added upon completion of issue 40
example, "File does not exist: /usr/local/docroot/nonexistent.html".
* SERVER_ADDR: This will typically be `::1` which is a unicast
- localhost address. This means that the packets sent to this addrress
+ localhost address. This means that the packets sent to this address
will be looped back on the same virtual interface.
-* SERVER_PORT: Port to which the request was performed origianlly.
+* SERVER_PORT: Port to which the request was performed originally.
* REMOTE_PORT: Port to which the request was served.
//////
@@ -34,6 +34,6 @@ image::media/images/admin_handler_custom_error.png[Handler Custom Error]
|501 |Not Implemented
|502 |Bad gateway
|503 |Service Unavailable
-|504 |Gatewat Timeout
+|504 |Gateway Timeout
|505 |HTTP Version Not Supported
|=====================================
@@ -76,6 +76,6 @@ group fails the rest will not be run. You will receive at least one
error among the results, which is probably all what you need in case
you were in the middle of a transaction or that sort of situation.
-Further information about this hanlder can be found in the
+Further information about this handler can be found in the
link:cookbook.html[cookbook] section, specifically in the recipe about
link:cookbook_dbslayer.html[setting up the MySQL balancing].
@@ -8,7 +8,7 @@ dispatches in-bound network traffic to a set of servers, and presents
a single interface to the requesters. This is particularly useful to
load balance a cluster of webservers at a much higher network stack
level than that allowed by the
-link:modules_hanlders_mirror.html[generic balancer].
+link:modules_handlers_mirror.html[generic balancer].
All connections coming from the Internet addressed to one of the Web
servers are routed through the proxy, which can either deal with the
@@ -34,7 +34,7 @@ steps.
image::media/images/proxy_phase1.png[Phase 1]
* Phase 2: Once the server that has received the request sends back the
- response, the reverse proxy deletes the unnecesary return HTTP
+ response, the reverse proxy deletes the unnecessary return HTTP
headers and sends the response back to the requesting client.
image::media/images/proxy_phase2.png[Phase 2]
@@ -5,7 +5,7 @@ Handler: Server Side Includes
Server Side Includes, also known as SSI, are directives placed in HTML
pages meant to be evaluated on the web server while the requests are
-being delivered. The intented use is adding some dynamic content to
+being delivered. The intended use is adding some dynamic content to
existing HTML pages without having to serve the whole content
dynamically (be it through CGI, SCGI, FastCGI, etc.).
@@ -17,7 +17,7 @@ extension.
Although this will be the majority of cases where this can be of
usefulness, Cherokee is not limited to just one file extension. The
-SSI hanlder applies to whatever is matched by the rule where it has
+SSI handler applies to whatever is matched by the rule where it has
been configured.
Currently Cherokee supports the following SSI directives:
@@ -57,7 +57,7 @@ directives like the following ones:
----
Note that the include element can determine what file to include based
-on the `virtual` or `file` attributes, which have the behavoir
+on the `virtual` or `file` attributes, which have the behavior
specified above. In any case, despite specifying absolute or relative
paths containing `..`, the SSI handler will not include any files
outside the webserver document root.
View
@@ -3,7 +3,7 @@
Modules: Loggers
----------------
-Loggers are a type of Cherokee modules unsurpisingly used to log
+Loggers are a type of Cherokee modules unsurprisingly used to log
events. They can be configured on a per virtual server basis through
each virtual server's `Logging` section.
@@ -23,15 +23,15 @@ Here is an example:
::ffff:127.0.0.1 - - [11/Aug/2008:16:17:58 +0000] "GET /index.html HTTP/1.1" 200 2633 "-" "Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1"
****
-The description of the aditional fields follows.
+The description of the additional fields follows.
Refer to the link:modules_loggers_ncsa.html[Common Log
Format] documentation for information about the rest of the fields.
*referrer* ("-") ::
-This is the "Referer" HTTP request header. This indicates the URL
+This is the "Referrer" HTTP request header. This indicates the URL
which linked the user to your site (as reported by the client). In
-this case it is empty because no referer exists (i.e. it is a direct
+this case it is empty because no Referrer exists (i.e. it is a direct
hit).
@@ -15,7 +15,7 @@ configured virtual server.
Depending on the complexity of the mechanism you will have to provide
more or less information.
-You will always have to provide a *Relam*, which is a name to
+You will always have to provide a *Realm*, which is a name to
associate with the authenticated resource.
You will also have permanently the option to provide a list of *allowed
users*, regardless of the validator chosen.
@@ -26,7 +26,7 @@ authentication mechanisms:
* Basic
* Digest
-Some can only handle one of those mechanisms because of techical
+Some can only handle one of those mechanisms because of technical
limitations. In case the module supports both of them, the interface
allows to choose whether one or both are to be used.
@@ -41,7 +41,7 @@ that perform the actual authentication tasks.
Cherokee's installation procedure already takes care of the creation
of such file (under /etc or whatever system configuration directory is
used in your platform of choice). If you consistently fail to use the
-PAM validator, make sure that such configuration deffinitions are set.
+PAM validator, make sure that such configuration definitions are set.
.Sample: /etc/pam.d/cherokee
----

0 comments on commit 3c112e2

Please sign in to comment.