openstack/neutron
Code Issues Proposed changes

Merge "Fix spelling mistakes in the docs"

Browse Source
This commit is contained in:
Jenkins 2016-06-30 18:59:18 +00:00 committed by Gerrit Code Review
commit eba3ddd682
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/devref/callbacks.rst
View File

@ -359,7 +359,7 @@ Is there any ordering guarantee during notifications?
notified. Priorities can be a future extension, if a use case arises that require enforced notified. Priorities can be a future extension, if a use case arises that require enforced
ordering. ordering.
How is the the notifying object expected to interact with the subscribing objects? How is the notifying object expected to interact with the subscribing objects?
The ``notify`` method implements a one-way communication paradigm: the notifier sends a message The ``notify`` method implements a one-way communication paradigm: the notifier sends a message
without expecting a response back (in other words it fires and forget). However, due to the nature without expecting a response back (in other words it fires and forget). However, due to the nature

2
doc/source/devref/tag.rst
View File

@ -41,7 +41,7 @@ can be applicable to any other Neutron resource:
3) Leverage tags by deployment tools 3) Leverage tags by deployment tools
4) allow operators to tag information about provider networks 4) allow operators to tag information about provider networks
(e.g. high-bandwith, low-latency, etc) (e.g. high-bandwidth, low-latency, etc)
5) new features like get-me-a-network or a similar port scheduler 5) new features like get-me-a-network or a similar port scheduler
could choose a network for a port based on tags could choose a network for a port based on tags