ITS#5759 whitespace vs white space - we now use whitespace.

This commit is contained in:
Gavin Henry 2008-10-30 13:49:11 +00:00
parent 66be548b58
commit df5196b745
3 changed files with 4 additions and 4 deletions

View file

@ -162,7 +162,7 @@ values (the server will only report the first error it finds).
Common causes include:
* extraneous white space (especially trailing white space)
* extraneous whitespace (especially trailing whitespace)
* improperly encoded characters (LDAPv3 uses UTF-8 encoded Unicode)
* empty values (few syntaxes allow empty values)

View file

@ -125,7 +125,7 @@ keywords, using the keyword as the attribute name, with the "olc"
prefix attached.
A configuration directive may take arguments. If so, the arguments are
separated by white space. If an argument contains white space,
separated by whitespace. If an argument contains whitespace,
the argument should be enclosed in double quotes {{EX:"like this"}}.
In the descriptions that follow, arguments that should be replaced
by actual text are shown in brackets {{EX:<>}}.

View file

@ -27,7 +27,7 @@ be overridden in backend and/or database directives, and backend directives
can be overridden by database directives.
Blank lines and comment lines beginning with a '{{EX:#}}' character
are ignored. If a line begins with white space, it is considered a
are ignored. If a line begins with whitespace, it is considered a
continuation of the previous line (even if the previous line is a
comment).
@ -56,7 +56,7 @@ The general format of slapd.conf is as follows:
> ...
A configuration directive may take arguments. If so, they are
separated by white space. If an argument contains white space,
separated by whitespace. If an argument contains whitespace,
the argument should be enclosed in double quotes {{EX:"like this"}}. If
an argument contains a double quote or a backslash character `{{EX:\}}',
the character should be preceded by a backslash character `{{EX:\}}'.