From 64fb61d37cbed6ee556bdcfda24df3ea74c198d7 Mon Sep 17 00:00:00 2001 From: Daisuke Fujita Date: Fri, 9 Oct 2015 22:20:51 +0900 Subject: [PATCH] Fix typo in rpc/server.py and notify/listener.py 1. "messaging configuration configuration" to "messaging configuration" Change-Id: Icda5d2df67cc4d2d0e0cb3a453d0b04dd998e5f4 --- oslo_messaging/notify/listener.py | 2 +- oslo_messaging/rpc/server.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/oslo_messaging/notify/listener.py b/oslo_messaging/notify/listener.py index 1aa4613f7..3460ef962 100644 --- a/oslo_messaging/notify/listener.py +++ b/oslo_messaging/notify/listener.py @@ -24,7 +24,7 @@ A transport can be obtained simply by calling the get_transport() method:: transport = messaging.get_transport(conf) which will load the appropriate transport driver according to the user's -messaging configuration configuration. See get_transport() for more details. +messaging configuration. See get_transport() for more details. The target supplied when creating a notification listener expresses the topic and - optionally - the exchange to listen on. See Target for more details diff --git a/oslo_messaging/rpc/server.py b/oslo_messaging/rpc/server.py index 7f6295b6b..855e3d9a6 100644 --- a/oslo_messaging/rpc/server.py +++ b/oslo_messaging/rpc/server.py @@ -25,7 +25,7 @@ A transport can be obtained simply by calling the get_transport() method:: transport = messaging.get_transport(conf) which will load the appropriate transport driver according to the user's -messaging configuration configuration. See get_transport() for more details. +messaging configuration. See get_transport() for more details. The target supplied when creating an RPC server expresses the topic, server name and - optionally - the exchange to listen on. See Target for more details