From d0364e048ba5bda8f6ada35ac42013f55de8d159 Mon Sep 17 00:00:00 2001 From: "Q.hongtao" Date: Fri, 6 Sep 2019 16:15:51 +0800 Subject: [PATCH] Fix misspell word Change-Id: I86a99f7e1cdc792ae30f92a614dad8b255a1f86a --- specs/juno/amqp10-driver-implementation.rst | 2 +- specs/newton/policy-in-code.rst | 2 +- specs/newton/policy-sample-generation.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/specs/juno/amqp10-driver-implementation.rst b/specs/juno/amqp10-driver-implementation.rst index eeed61e..665b71b 100644 --- a/specs/juno/amqp10-driver-implementation.rst +++ b/specs/juno/amqp10-driver-implementation.rst @@ -165,7 +165,7 @@ users. It does however restrict choice. Another alternative would be to choose a different protocol as the basis of the new driver. MQTT is focused on a pub-sub pattern and doesn't incorporate competing consumers as is required for the current -olso.messaging semantics. STOMP doesn't define interoperable +oslo.messaging semantics. STOMP doesn't define interoperable mechanisms for request-response. Since two of the existing drivers use earlier versions of AMQP, AMQP supports all the patterns needed and AMQP is an open standard (now standardised under ISO) it seems a diff --git a/specs/newton/policy-in-code.rst b/specs/newton/policy-in-code.rst index f007421..d2214c5 100644 --- a/specs/newton/policy-in-code.rst +++ b/specs/newton/policy-in-code.rst @@ -125,7 +125,7 @@ will initially hold rulenames, rules, and descriptions. Files to change: -* olso_policy/policy.py +* oslo_policy/policy.py Alternatives ------------ diff --git a/specs/newton/policy-sample-generation.rst b/specs/newton/policy-sample-generation.rst index 3c2102c..9afd37b 100644 --- a/specs/newton/policy-sample-generation.rst +++ b/specs/newton/policy-sample-generation.rst @@ -52,7 +52,7 @@ deployers maintain and trim their policy files. Files to change: -* olso_policy/generator.py (new file) +* oslo_policy/generator.py (new file) * setup.cfg (register an entry point) Alternatives