openstack
/
designate-specs
Code Issues Proposed changes

Fix typo in zone-exists-event.rst 

line #33: s/current;y/currently
line #34: s/demaining/demanding

Change-Id: I1967b56c509d7187b2dba9dc392bf1cb18ddf05b
This commit is contained in:
Naveen Chekuri 2016-07-26 23:54:08 -07:00
parent 7d72369fe9
commit ca98f45df6
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
specs/liberty/zone-exists-event.rst
View File

@ -30,8 +30,8 @@ In other services like Nova there is a clear "owner" for each core resource
each nova-compute instance to periodically emit a `compute.instance.exists`
event for a small number of instances. Designate has no such clear owner,
and many thousands of zones may belong to a single pool (the smallest
grouping we current;y have available). This poses a problem, in that emitting
100's of thousands of events, or more, each hour may be too demaining for the
grouping we currently have available). This poses a problem, in that emitting
100's of thousands of events, or more, each hour may be too demanding for the
active pool manager.
Proposed change