doc: Fixed some typos.

[ashd.git] / doc / dirplex.doc

diff --git a/doc/dirplex.doc b/doc/dirplex.doc
index 048548a..8a0184f 100644 (file)
--- a/doc/dirplex.doc
+++ b/doc/dirplex.doc
@@ -71,7 +71,7 @@ element. If there is such a file, it is considered the result of the
 mapping.
 
 If the result of the mapping procedure is a directory, it is checked
 mapping.
 
 If the result of the mapping procedure is a directory, it is checked

-for the presence of a filed named by the *index-file* configuration
+for the presence of a file named by the *index-file* configuration

 directive (see CONFIGURATION below). If there is such a file, it is
 considered the final result instead of the directory itself. If the
 index file name contains no dots and there is no exact match, then,
 directive (see CONFIGURATION below). If there is such a file, it is
 considered the final result instead of the directory itself. If the
 index file name contains no dots and there is no exact match, then,


@@ -193,9 +193,10 @@ The following configuration directives are recognized:
        be a named request handler specified either in the same
        `.htrc` file or elsewhere. The *capture* directive accepts no
        follow-up lines. Note that the `X-Ash-File` header is not
        be a named request handler specified either in the same
        `.htrc` file or elsewhere. The *capture* directive accepts no
        follow-up lines. Note that the `X-Ash-File` header is not

-       added to requests passed via *capture* directives.  If 'FLAGS'
-       contain the character `R`, this *capture* directive will be
-       ignored if it is in the root directory that *dirplex* serves.
+       added to requests passed via *capture* directives. Normally,
+       *capture* directives will be ignored if they appear in the
+       root directory that *dirplex* serves, but not if 'FLAGS'
+       contain the character `D`.

 
 MATCHING
 --------
 
 MATCHING
 --------


@@ -213,7 +214,7 @@ in the global configuration files are searched in order of their
 *match* stanzas are considered depends on the type of the file being
 matched: if an ordinary file is being matched, only *match* stanzas
 without any 'TYPE' parameter are considered, while if it is a
 *match* stanzas are considered depends on the type of the file being
 matched: if an ordinary file is being matched, only *match* stanzas
 without any 'TYPE' parameter are considered, while if it is a

-directory, only those with type 'TYPE' parameter specified as
+directory, only those with the 'TYPE' parameter specified as

 *directory* are considered. 'TYPE' can also take the value *notfound*,
 described below under 404 RESPONSES.
 
 *directory* are considered. 'TYPE' can also take the value *notfound*,
 described below under 404 RESPONSES.
 


@@ -294,7 +295,7 @@ A HTTP 404 response is sent to the client if
  * A path element is encountered during mapping which, after URL
    unescaping, either begins with a dot or contains slashes;
  * The mapping procedure finds a file which is neither a directory nor
  * A path element is encountered during mapping which, after URL
    unescaping, either begins with a dot or contains slashes;
  * The mapping procedure finds a file which is neither a directory nor

-   a regular file (or a symbolic link to any of the same);
+   a regular file (nor a symbolic link to any of the same);

  * An empty, non-final path element is encountered during mapping; or
  * The mapping procedure results in a file which is not matched by any
    *match* stanza.
  * An empty, non-final path element is encountered during mapping; or
  * The mapping procedure results in a file which is not matched by any
    *match* stanza.