From 9157ed503b74609b1640cd3cd7b9979099b8ed0a Mon Sep 17 00:00:00 2001 From: Gary Kotton Date: Wed, 29 Jun 2016 05:30:29 -0700 Subject: [PATCH] Update documents to address some issues Issues: 1. typo 'Defintions' => 'Definitions' 2. change 'the the' => 'the' TrivialFix Change-Id: I71f6b3159520ca5d80e4758a34389854f1b05c7d --- doc/source/devref/api_converters.rst | 2 +- doc/source/devref/callbacks.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/devref/api_converters.rst b/doc/source/devref/api_converters.rst index a44cf5a99..8288c4257 100644 --- a/doc/source/devref/api_converters.rst +++ b/doc/source/devref/api_converters.rst @@ -24,7 +24,7 @@ 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 can be used. diff --git a/doc/source/devref/callbacks.rst b/doc/source/devref/callbacks.rst index 3ddbca4ca..5a2ba95c5 100644 --- a/doc/source/devref/callbacks.rst +++ b/doc/source/devref/callbacks.rst @@ -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 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 without expecting a response back (in other words it fires and forget). However, due to the nature