openstack/designate
Code Issues Proposed changes

Fix some spelling

Browse Source 
Change-Id: Iaf11303ac43879ffaee0782a0910280e932e7d04
Signed-off-by: Nicolas Bock <nicolas.bock@canonical.com>
This commit is contained in:
Nicolas Bock 2020-06-01 09:11:07 -06:00
parent da48d94dcb
commit 92ae4a9456
No known key found for this signature in database
GPG Key ID: ACE86353C0EF022A
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/admin/backends/infoblox.rst
View File

@ -32,7 +32,7 @@ Infoblox Configuration
----------------------
* Create a user for use by Designate.
* Set up one or more name server groups to be used to serve Designate zones.
* Set up one or more nameserver groups to be used to serve Designate zones.
* Set the Designate mDNS servers as external primaries
* Add a grid member as a grid secondary; select the "Lead Secondary" option

2
doc/source/admin/pools.rst
View File

@ -25,7 +25,7 @@ Overview
In designate we support the concept of multiple "pools" of DNS Servers.
This allows operators to scale out their DNS Service by adding more pools,
avoiding the scalling problems that some DNS servers have for number of zones,
avoiding the scaling problems that some DNS servers have for number of zones,
and the total number of records hosted by a single server.
This also allows providers to have tiers of service (i.e. the difference