[Trivial] Fix some typos in designate.
Change-Id: I664b65d5c91b991b478c012955ccc1be94599c86
This commit is contained in:
parent
4d383a30e9
commit
89033f080b
|
@ -408,7 +408,7 @@ class ZonePoller(base.Task, ThresholdMixin):
|
|||
- ERROR: the operation failed
|
||||
- NO_ZONE: the zone doesn't exist on enough name servers
|
||||
|
||||
:return: Whether the the polling was succesful, and a status
|
||||
:return: Whether the the polling was successful, and a status
|
||||
describing the state (bool, str)
|
||||
"""
|
||||
|
||||
|
|
|
@ -20,7 +20,7 @@
|
|||
|
||||
Designate supports "pools" of nameservers. A pool is a collection of
|
||||
nameservers and targets that Designate will write to and read from to
|
||||
confirm changes are successfull. In some cases you might have multiple
|
||||
confirm changes are successful. In some cases you might have multiple
|
||||
pools that you need to manage differently. For example, you might use
|
||||
separate pools to distribute tenants across some subset of your DNS
|
||||
infrastructure.
|
||||
|
|
|
@ -46,7 +46,7 @@ external facing zones.
|
|||
|
||||
To help users create zones on the correct pool we have a "scheduler" that is
|
||||
responsible for examining the zone being created and the pools that are
|
||||
availible for use, and matching the zone to a pool.
|
||||
available for use, and matching the zone to a pool.
|
||||
|
||||
The filters are pluggable (i.e. operator replaceable) and all follow a simple
|
||||
interface.
|
||||
|
|
Loading…
Reference in New Issue