[multiple] correct misspellings in comments

x-ref:
  "Script for fixing spelling errors with codespell"
  https://redmine.lighttpd.net/boards/3/topics/8947

16 files changed, 59 insertions, 59 deletions

diff --git a/doc/outdated/accesslog.txt b/doc/outdated/accesslog.txt
index 889a4daa..ad0f4543 100644
--- a/doc/outdated/accesslog.txt
+++ b/doc/outdated/accesslog.txt
@@ -70,7 +70,7 @@ accesslog.format
   %C     cookie field (not supported)
   %D     time used in ms (not supported)
   %e     environment (not supported)
-  %f     phyiscal filename
+  %f     physical filename
   %H     request protocol (HTTP/1.0, ...)
   %m     request method (GET, POST, ...)
   %n     (not supported)
@@ -83,7 +83,7 @@ accesslog.format
   %v     server-name
   %V     (not supported)
   %X     connection status
-  %I     bytes incomming
+  %I     bytes incoming
   %O     bytes outgoing
   ====== ================================
 
diff --git a/doc/outdated/authentication.txt b/doc/outdated/authentication.txt
index 6fbd7764..3e2e7011 100644
--- a/doc/outdated/authentication.txt
+++ b/doc/outdated/authentication.txt
@@ -37,7 +37,7 @@ basic
 
 The Basic method transfers the username and the password in
 cleartext over the network (base64 encoded) and might result
-in security problems if not used in conjunction with a crypted
+in security problems if not used in conjunction with an encrypted
 channel between client and server.
 
 digest
@@ -70,7 +70,7 @@ plain
 `````
 
 A file which contains username and the cleartext password
-seperated by a colon. Each entry is terminated by a single
+separated by a colon. Each entry is terminated by a single
 newline.::
 
   e.g.:
@@ -81,7 +81,7 @@ htpasswd
 ````````
 
 A file which contains username and the crypt()'ed password
-seperated by a colon. Each entry is terminated by a single
+separated by a colon. Each entry is terminated by a single
 newline. ::
 
   e.g.:
@@ -97,7 +97,7 @@ htdigest
 ````````
 
 A file which contains username, realm and the md5()'ed
-password seperated by a colon. Each entry is terminated
+password separated by a colon. Each entry is terminated
 by a single newline. ::
 
   e.g.:
@@ -188,13 +188,13 @@ Configuration
   auth.require = ( "/download/" =>
                    (
 		     "method"  => "digest",
-		     "realm"   => "download archiv",
+		     "realm"   => "download archive",
 		     "require" => "user=agent007|user=agent008"
 		   ),
 		   "/server-info" =>
                    (
 		     "method"  => "digest",
-		     "realm"   => "download archiv",
+		     "realm"   => "download archive",
 		     "require" => "valid-user"
 		   )
                  )
diff --git a/doc/outdated/cml.txt b/doc/outdated/cml.txt
index 32ae1d5d..b9ae92c5 100644
--- a/doc/outdated/cml.txt
+++ b/doc/outdated/cml.txt
@@ -26,7 +26,7 @@ CML (Cache Meta Language) wants to solves several problems:
  * dynamic content needs caching to perform
  * checking if the content is dirty inside of the application is usually more expensive than sending out the cached data
  * a dynamic page is usually fragmented and the fragments have different livetimes
- * the different fragements can be cached independently
+ * the different fragments can be cached independently
 
 Cache Decision
 --------------
@@ -163,7 +163,7 @@ Next to all the features about Cache Decisions CML can do more. Starting
 with lighttpd 1.4.9 a power-magnet was added which attracts each request
 and allows you to manipulate the request for your needs.
 
-We want to display a maintainance page by putting a file in a specified
+We want to display a maintenance page by putting a file in a specified
 place:
 
 We enable the power magnet: ::
@@ -174,15 +174,15 @@ and create /home/www/power-magnet.cml with: ::
 
   dr = request["DOCUMENT_ROOT"]
 
-  if file_isreg(dr .. 'maintainance.html') then
-    output_include = { 'maintainance.html' }
+  if file_isreg(dr .. 'maintenance.html') then
+    output_include = { 'maintenance.html' }
     return CACHE_HIT
   end
 
   return CACHE_MISS
 
 For each requested file the /home/www/power-magnet.cml is executed which
-checks if maintainance.html exists in the docroot and displays it
+checks if maintenance.html exists in the docroot and displays it
 instead of handling the usual request.
 
 Another example, create thumbnail for requested image and serve it instead
@@ -256,6 +256,6 @@ Additionally to the functions provided by lua mod_cml provides: ::
 
 
 What ever your script does, it has to return either CACHE_HIT or CACHE_MISS.
-It case a error occures check the error-log, the user will get a error 500. If you don't like
+It case a error occurs check the error-log, the user will get a error 500. If you don't like
 the standard error-page use ``server.errorfile-prefix``.
 
diff --git a/doc/outdated/compress.txt b/doc/outdated/compress.txt
index 14fbc2dc..d2e83bbf 100644
--- a/doc/outdated/compress.txt
+++ b/doc/outdated/compress.txt
@@ -110,7 +110,7 @@ Display compressed files
 ========================
 
 If you enable mod_compress, and you want to force clients to uncompress and display compressed text files, please force mimetype to nothing.
-Exemple :
+Example :
 If you want to add headers for uncompress and display diff.gz files , add this section in your conf : ::
 
   $HTTP["url"] =~ "\.diff\.gz" {
diff --git a/doc/outdated/configuration.txt b/doc/outdated/configuration.txt
index bd84c913..536e89e7 100644
--- a/doc/outdated/configuration.txt
+++ b/doc/outdated/configuration.txt
@@ -188,7 +188,7 @@ You can set your own variables in the configuration to simplify your config.
   server.document-root = basedir + server.name + "/pages/"
   accesslog.filename   = basedir + server.name + "/logs/access.log"
 
-You can also use environement variables or the default variables var.PID and
+You can also use environment variables or the default variables var.PID and
 var.CWD: ::
 
   var.basedir = env.LIGHTTPDBASE
@@ -380,7 +380,7 @@ server.modules
  				"mod_rrdtool",
 				"mod_accesslog" )
 
-  Starting with lighttpd 1.4.0 three default modules are loaded automaticly:
+  Starting with lighttpd 1.4.0 three default modules are loaded automatically:
 
   - mod_indexfile
   - mod_dirlisting
@@ -422,7 +422,7 @@ server.max-keep-alive-requests
   Default: 128
 
 server.max-keep-alive-idle
-  maximum number of seconds until a idling keep-alive connection is droped
+  maximum number of seconds until a idling keep-alive connection is dropped
 
   Default: 30
 
diff --git a/doc/outdated/dirlisting.txt b/doc/outdated/dirlisting.txt
index 5dd6873d..923db8c5 100644
--- a/doc/outdated/dirlisting.txt
+++ b/doc/outdated/dirlisting.txt
@@ -106,12 +106,12 @@ dir-listing.set-footer
   Default: empty, uses server.tag instead
 
 dir-listing.encode-readme
-  encodes all control characers, '&', '<', '>' and '\x7f' as &#x**;
+  encodes all control characters, '&', '<', '>' and '\x7f' as &#x**;
 
   Default: enabled
 
 dir-listing.encode-header
-  encodes all control characers, '&', '<', '>' and '\x7f' as &#x**;
+  encodes all control characters, '&', '<', '>' and '\x7f' as &#x**;
 
   Default: enabled
 
diff --git a/doc/outdated/expire.txt b/doc/outdated/expire.txt
index ca59c42a..acc84f53 100644
--- a/doc/outdated/expire.txt
+++ b/doc/outdated/expire.txt
@@ -22,14 +22,14 @@ Description
 ===========
 
 mod_expire controls the Expire header in the Response Header of HTTP/1.0
-messages. It is usefull to set it for static files which should be cached
+messages. It is useful to set it for static files which should be cached
 aggressivly like images, stylesheets or similar.
 
 Options
 =======
 
 expire.url
-  assignes a expiration to all files below the specified path. The
+  assign a expiration to all files below the specified path. The
   specification of the time is made up of: ::
 
     <access|modification> <number> <years|months|days|hours|minutes|seconds>
diff --git a/doc/outdated/fastcgi.txt b/doc/outdated/fastcgi.txt
index ee3c0b92..7ae85ba2 100644
--- a/doc/outdated/fastcgi.txt
+++ b/doc/outdated/fastcgi.txt
@@ -152,14 +152,14 @@ fastcgi.server
 
   If bin-path is set:
 
-  :"max-procs": the upper limit of the processess to start
+  :"max-procs": the upper limit of the processes to start
   :"bin-environment": put an entry into the environment of
                 the started process
   :"bin-copy-environement": clean up the environment and copy
                 only the specified entries into the fresh
                 environment of the spawn process
   :"kill-signal": signal to terminate the FastCGI process with,
-                defauls to SIGTERM
+                defaults to SIGTERM
 
 Examples
 --------
@@ -193,7 +193,7 @@ Examples
   "/remote_scripts/test.cgi" will be used for the SCRIPT_NAME
   variable. Remote server may prepend it with its own
   document root. The handling of index files is also the
-  resposibility of remote server for this case.
+  responsibility of remote server for this case.
 
   In the case that the prefix is not terminated with a slash
   the prefix will be handled as file and /test.cgi would become
@@ -217,7 +217,7 @@ Examples
 Load-Balancing
 ==============
 
-The FastCGI plugin provides automaticly a load-balancing between
+The FastCGI plugin provides automatically a load-balancing between
 multiple FastCGI servers. ::
 
   fastcgi.server = ( ".php" =>
@@ -243,7 +243,7 @@ fastcgi.debug option and will get a similar output as here: ::
   proc: 127.0.0.1 1029  1 1 2 31447
 
 Even if this for multiple FastCGI children on the local machine
-the following explaination is valid for remote connections too.
+the following explanation is valid for remote connections too.
 
 The output shows:
 
@@ -303,7 +303,7 @@ Disabling Adaptive Spawning
 ---------------------------
 
 Adaptive Spawning is a quite new feature and it might misbehave
-for your setup. There are several ways to control how the spawing
+for your setup. There are several ways to control how the spawning
 is done:
 
 1. ``"max-load-per-proc" => 1``
@@ -351,7 +351,7 @@ webserver execute a small script which just contains ::
 and search for the line in that contains the configure call.
 You can use it as the base for the compilation.
 
-You have to remove all occurences of `--with-apxs`, `--with-apxs2`
+You have to remove all occurrences of `--with-apxs`, `--with-apxs2`
 and the like which would build PHP with Apache support.  Add the
 next three switches to compile PHP with FastCGI support::
 
@@ -382,7 +382,7 @@ processes locally itself if necessary: ::
   )
 
 PHP provides 2 special environment variables which control the number of
-spawned workes under the control of a single watching process
+spawned works under the control of a single watching process
 (PHP_FCGI_CHILDREN) and the number of requests what a single worker
 handles before it kills itself. ::
 
@@ -449,7 +449,7 @@ disadvantages like
 - has the same permissions as the webserver
 - has the same base-dir as the webserver
 
-As soon as you are using a seperate FastCGI Server to
+As soon as you are using a separate FastCGI Server to
 take off some load from the webserver you have to control
 the FastCGI process by a external program like spawn-fcgi.
 
@@ -476,14 +476,14 @@ a look at: ::
   ## bind to unix domain socket
   # FCGISOCKET="/tmp/php.sock"
 
-  ## number of PHP childs to spawn
+  ## number of PHP children to spawn
   PHP_FCGI_CHILDREN=10
 
   ## number of request server by a single php-process until
   ## is will be restarted
   PHP_FCGI_MAX_REQUESTS=1000
 
-  ## IP adresses where PHP should access server connections
+  ## IP addresses where PHP should access server connections
   ## from
   FCGI_WEB_SERVER_ADDRS="127.0.0.1,192.168.0.1"
 
@@ -512,7 +512,7 @@ in your processlist: ::
 The number of processes should be PHP_FCGI_CHILDREN + 1.
 Here the process 6925 is the master of the slaves which
 handle the work in parallel. Number of parallel workers can
-be set by PHP_FCGI_CHILDREN. A worker dies automaticly of
+be set by PHP_FCGI_CHILDREN. A worker dies automatically of
 handling PHP_FCGI_MAX_REQUESTS requests as PHP might have
 memory leaks.
 
@@ -524,7 +524,7 @@ the user you started script as.
 As the script might be started from a unknown stage or even
 directly from the command-line it cleans the environment
 before starting the processes. ALLOWED_ENV contains all
-the external environement variables that should be available
+the external environment variables that should be available
 to the php-process.
 
 
@@ -600,5 +600,5 @@ If you get ::
   (fcgi.c.289) connect succeeded:  7
 
 everything is fine. The connect() call just was delayed a
-little bit and is completly normal.
+little bit and is completely normal.
 
diff --git a/doc/outdated/features.txt b/doc/outdated/features.txt
index f45fe08b..04a1aec2 100644
--- a/doc/outdated/features.txt
+++ b/doc/outdated/features.txt
@@ -43,7 +43,7 @@ Constantly improving. ::
   The configuration syntax is overly complex, like Apache.  There is no .htaccess
   support.
 
-.htaccess support is not planed yet. ::
+.htaccess support is not planned yet. ::
 
   There is only one server.  You cannot have a separate configuration for each
   virtual server.  This would seem to be especially problematic when doing
@@ -65,7 +65,7 @@ SSI works since 1.2.4. ::
   Access control only allows authentication via username and password.  There
   is no way to allow or deny based in IP address.
 
-planed for 1.3.x ::
+planned for 1.3.x ::
 
   The request rewriting appears to only allow regex substitutions.  Zeus has a
   simple, yet powerful, request rewrite language.
diff --git a/doc/geoip.txt b/doc/outdated/geoip.txt
index 99b0ed09..a3d39bc3 100644
--- a/doc/geoip.txt
+++ b/doc/outdated/geoip.txt
@@ -45,7 +45,7 @@ memory for very fast lookups. the only penalty is memory usage.
 .. note::
 
  mod_geoip will determine the database type automatically so if you enter
- GeoCity databse path it will load GeoCity Env.
+ GeoCity database path it will load GeoCity Env.
 
 Environment
 ===========
@@ -139,7 +139,7 @@ redirect.php ::
 .. note::
 
  Currently it is not possible to redirect based on mod_geoip directly in
-lighttpd config file. But i believe with the relase of lighttpd mod_magnet
+lighttpd config file. But i believe with the release of lighttpd mod_magnet
 it would be. (mod_magnet will be available in lighttpd 1.4.12+)
 
 Downloads
diff --git a/doc/outdated/magnet.txt b/doc/outdated/magnet.txt
index 0559174f..c7e24c5b 100644
--- a/doc/outdated/magnet.txt
+++ b/doc/outdated/magnet.txt
@@ -29,7 +29,7 @@ mod_magnet is a module to control the request handling in lighty.
   ALL connections in the server. You are warned. For time-consuming or blocking scripts use mod_fastcgi and friends.
 
 For performance reasons mod_magnet caches the compiled script. For each script-run the script itself is checked for 
-freshness and recompile if neccesary.
+freshness and recompile if necessary.
 
 
 Installation
@@ -85,7 +85,7 @@ When you are using ``attract-raw-url-to`` you can access the following variables
 
   * lighty.request["Host"] = "example.org"
 
-Later in the request-handling, the URL is splitted, cleaned up and turned into a physical path name:
+Later in the request-handling, the URL is split, cleaned up and turned into a physical path name:
 
 * parts of the URI
 
@@ -149,7 +149,7 @@ Internally lighty will use the sendfile() call to send out the static files at f
 Status Codes
 ============
 
-You might have seen it already in other examples: In case you are handling the request completly in the magnet you
+You might have seen it already in other examples: In case you are handling the request completely in the magnet you
 can return your own status-codes. Examples are: Redirected, Input Validation, ... ::
 
   if (lighty.env["uri.scheme"] == "http") then
@@ -193,22 +193,22 @@ readme.lua ::
   
   return 200
 
-Maintainance pages
+Maintenance pages
 ------------------
 
-Your side might be on maintainance from time to time. Instead of shutting down the server confusing all
-users, you can just send a maintainance page.
+Your side might be on maintenance from time to time. Instead of shutting down the server confusing all
+users, you can just send a maintenance page.
 
 Config-file ::
 
-  magnet.attract-physical-path-to = server.docroot + "/maintainance.lua"
+  magnet.attract-physical-path-to = server.docroot + "/maintenance.lua"
 
-maintainance.lua ::
+maintenance.lua ::
 
   require "lfs"
 
-  if (nil == lfs.attributes(lighty.env["physical.doc-root"] .. "/maintainance.html")) then
-    lighty.content = ( lighty.env["physical.doc-root"] .. "/maintainance.html" )
+  if (nil == lfs.attributes(lighty.env["physical.doc-root"] .. "/maintenance.html")) then
+    lighty.content = ( lighty.env["physical.doc-root"] .. "/maintenance.html" )
 
     lighty.header["Content-Type"] = "text/html"
 
@@ -234,7 +234,7 @@ flv-streaming.lua::
     if (get["start"]) then
       -- missing: check if start is numeric and positive
 
-      -- send te FLV header + a seek into the file
+      -- send the FLV header + a seek into the file
       lighty.content = { "FLV\x1\x1\0\0\0\x9\0\0\0\x9", 
          { filename = lighty.env["physical.path"], offset = get["start"] } }
       lighty.header["Content-Type"] = "video/x-flv"
diff --git a/doc/outdated/rewrite.txt b/doc/outdated/rewrite.txt
index a1390695..cd51d5ec 100644
--- a/doc/outdated/rewrite.txt
+++ b/doc/outdated/rewrite.txt
@@ -27,14 +27,14 @@ Options
 =======
 
 url.rewrite-once
-  rewrites a set of URLs interally in the webserver BEFORE they are handled.
+  rewrites a set of URLs internally in the webserver BEFORE they are handled.
 
   e.g. ::
 
     url.rewrite-once = ( "<regex>" => "<relative-uri>" )
 
 url.rewrite-repeat
-  rewrites a set of URLs interally in the webserver BEFORE they are handled
+  rewrites a set of URLs internally in the webserver BEFORE they are handled
 
   e.g. ::
 
diff --git a/doc/outdated/secdownload.txt b/doc/outdated/secdownload.txt
index 21629983..6b2de072 100644
--- a/doc/outdated/secdownload.txt
+++ b/doc/outdated/secdownload.txt
@@ -56,7 +56,7 @@ A simple way to combine the two ways could be:
 
 1. app authenticates user and checks permissions to
    download the file.
-2. app redirects user to the file accessable by the webserver
+2. app redirects user to the file accessible by the webserver
    for further downloading.
 3. the webserver transfers the file to the user.
 
diff --git a/doc/outdated/ssi.txt b/doc/outdated/ssi.txt
index c65e7e17..f01e309f 100644
--- a/doc/outdated/ssi.txt
+++ b/doc/outdated/ssi.txt
@@ -11,7 +11,7 @@ Module: mod_ssi
 :Revision: $Revision: 1.2 $
 
 :abstract:
-  The module for server-side includes provides a compatability
+  The module for server-side includes provides a compatibility
   layer for NSCA/Apache SSI.
 
 .. meta::
diff --git a/doc/outdated/state.txt b/doc/outdated/state.txt
index 5e8277bd..ce98b74e 100644
--- a/doc/outdated/state.txt
+++ b/doc/outdated/state.txt
@@ -105,8 +105,8 @@ read all the delay packet from the network.
 Sub-Requests (lightblue)
 ------------------------
 
-The FastCGI, CGI, ... intergration is done by introducing a loop in
-'handlereq' to handle all aspect which are neccesary to find out what has
+The FastCGI, CGI, ... integration is done by introducing a loop in
+'handlereq' to handle all aspect which are necessary to find out what has
 to be sent back to the client.
 
 Functions
diff --git a/doc/outdated/status.txt b/doc/outdated/status.txt
index 53121768..7eb15565 100644
--- a/doc/outdated/status.txt
+++ b/doc/outdated/status.txt
@@ -52,8 +52,8 @@ Or require authorization: ::
     ( "realm" ... ) )
 
 
-Please note that when using the server.max-worker directive, the stati of the
-childs are not combined yet, so you're going to see different stats with each
+Please note that when using the server.max-worker directive, the status of the
+children are not combined yet, so you're going to see different stats with each
 request.