openstack
/
zaqar-specs
Code Issues Proposed changes

[Trivialfix]Fix typos 

Fix the typos found in zaqar-specs.

Change-Id: Ia072c6f313a885418dcd96df27586e87f36f3fb0
This commit is contained in:
shangxiaobj 2017-09-07 23:38:20 -07:00
parent c7da52e084
commit db9f53ed4f
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/kilo/fifo-optional.rst
View File

@ -16,7 +16,7 @@ Make FIFO guarantee optional
FIFO has been one of Zaqar's most wanted guarantees. Besides
reliability, durability and other latency requirements, users have
always requested FIFO to be there. This feature, however, has proven
to be an issue for some scenarios that don't necesarily require it,
to be an issue for some scenarios that don't necessarily require it,
hence this proposal.
https://blueprints.launchpad.net/zaqar/+spec/make-fifo-optional

4
specs/newton/mistral-notifications.rst
View File

@ -60,9 +60,9 @@ as well as a number of other actions (some of which, like sending email and
webhooks, are similar to Zaqar's notifications).
The missing link to build fully autonomous applications is for messages
(potentially, but not neccessarily originating from the OpenStack cloud itself)
(potentially, but not necessarily originating from the OpenStack cloud itself)
on Zaqar queues to be able to trigger Mistral workflows (potentially, but not
neccessarily calling other OpenStack APIs). This would give developers of cloud
necessarily calling other OpenStack APIs). This would give developers of cloud
applications an extremely flexible way of plugging together event-driven,
application-specific, autonomous actions.