Update documents to address some issues
Issues: 1. typo 'Defintions' => 'Definitions' 2. change 'the the' => 'the' TrivialFix Change-Id: I71f6b3159520ca5d80e4758a34389854f1b05c7d
This commit is contained in:
@@ -24,7 +24,7 @@
|
|||||||
API Converters
|
API Converters
|
||||||
==============
|
==============
|
||||||
|
|
||||||
Defintions for REST API attributes, can include conversion methods
|
Definitions for REST API attributes, can include conversion methods
|
||||||
to help normalize user input or transform the input into a form that
|
to help normalize user input or transform the input into a form that
|
||||||
can be used.
|
can be used.
|
||||||
|
|
||||||
|
|||||||
@@ -345,7 +345,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
|
||||||
|
|||||||
Reference in New Issue
Block a user