summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Nemec <bnemec@redhat.com>2018-11-02 17:53:40 +0000
committerBen Nemec <bnemec@redhat.com>2018-11-02 17:53:40 +0000
commit70d4047775efd902adf8222c0bbcd4d435a987e3 (patch)
tree5612b28547514c02fca7307081bb6f3edcd9b521
parent76fd7231cbd90812f38ea6cb8851472a8abdb56a (diff)
downloadoslo-config-70d4047775efd902adf8222c0bbcd4d435a987e3.tar.gz
Clean up grammar and spelling in driver docs
Was just looking at these and noticed that they're a bit difficult to parse due to some grammar and spelling issues. Change-Id: I9bc87ecc730474147e6e06c3faa5eb44a33f81a9
-rw-r--r--oslo_config/sources/__init__.py8
1 files changed, 4 insertions, 4 deletions
diff --git a/oslo_config/sources/__init__.py b/oslo_config/sources/__init__.py
index 0accdea..a37c6c4 100644
--- a/oslo_config/sources/__init__.py
+++ b/oslo_config/sources/__init__.py
@@ -13,16 +13,16 @@ r"""
Oslo.config's primary source of configuration data are plaintext, INI-like
style, configuration files. With the addition of backend drivers support,
it is possible to store configuration data in different places and with
-different formats, as long as, exists a proper driver to connect to those
-external sources and provides a way to fetch configuration values from them.
+different formats, as long as there exists a proper driver to connect to those
+external sources and provide a way to fetch configuration values from them.
A backend driver implementation is divided in two main classes, a driver
class of type :class:`ConfigurationSourceDriver` and a configuration source
class of type :class:`ConfigurationSource`.
**IMPORTANT:** At this point, all backend drivers are only able to provide
-unmutable values, this protects applications and services to have options
-from external sources mutaded when they reload configuration files.
+immutable values. This protects applications and services from having options
+in external sources mutated when they reload configuration files.
Abstract Classes
----------------