Commit 0b3b67e6 authored by Jim Fulton's avatar Jim Fulton

spelling

parent c61b5eaa
...@@ -18,7 +18,7 @@ ...@@ -18,7 +18,7 @@
<description> <description>
If supplied, the file storage will provide blob support and this If supplied, the file storage will provide blob support and this
is the name of a directory to hold blob data. The directory will is the name of a directory to hold blob data. The directory will
be created if it doeesn't exist. If no value (or an empty value) be created if it doesn't exist. If no value (or an empty value)
is provided, then no blob support will be provided. (You can still is provided, then no blob support will be provided. (You can still
use a BlobStorage to provide blob support.) use a BlobStorage to provide blob support.)
</description> </description>
...@@ -193,14 +193,14 @@ ...@@ -193,14 +193,14 @@
<key name="read-only-fallback" datatype="boolean" default="off"> <key name="read-only-fallback" datatype="boolean" default="off">
<description> <description>
A flag indicating whether a read-only remote storage should be A flag indicating whether a read-only remote storage should be
acceptable as a fallback when no writable storages are acceptable as a fall-back when no writable storages are
available. Defaults to false. At most one of read_only and available. Defaults to false. At most one of read_only and
read_only_fallback should be true. read_only_fallback should be true.
</description> </description>
</key> </key>
<key name="username" required="no"> <key name="username" required="no">
<description> <description>
The authentication username of the server. The authentication user name of the server.
</description> </description>
</key> </key>
<key name="password" required="no"> <key name="password" required="no">
...@@ -211,7 +211,7 @@ ...@@ -211,7 +211,7 @@
<key name="realm" required="no"> <key name="realm" required="no">
<description> <description>
The authentication realm of the server. Some authentication The authentication realm of the server. Some authentication
schemes use a realm to identify the logic set of usernames schemes use a realm to identify the logic set of user names
that are accepted by this server. that are accepted by this server.
</description> </description>
</key> </key>
...@@ -308,12 +308,12 @@ ...@@ -308,12 +308,12 @@
</key> </key>
<key name="database-name"> <key name="database-name">
<description> <description>
When multidatabases are in use, this is the name given to this When multi-databases are in use, this is the name given to this
database in the collection. The name must be unique across all database in the collection. The name must be unique across all
databases in the collection. The collection must also be given databases in the collection. The collection must also be given
a mapping from its databases' names to their databases, but that a mapping from its databases' names to their databases, but that
cannot be specified in a ZODB config file. Applications using cannot be specified in a ZODB config file. Applications using
multidatabases typical supply a way to configure the mapping in multi-databases typical supply a way to configure the mapping in
their own config files, using the "databases" parameter of a DB their own config files, using the "databases" parameter of a DB
constructor. constructor.
</description> </description>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment