From: ting.wang Date: Wed, 25 Nov 2015 08:43:01 +0000 (+0000) Subject: fix some misspellings X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=c42f9d3a6dd1b9d356c44b542b4714407407eaf1;p=openstack-build%2Fneutron-build.git fix some misspellings Change-Id: Ib6a027666dba060d12da7ecf918449c5ad62d239 --- diff --git a/doc/source/devref/upgrade.rst b/doc/source/devref/upgrade.rst index 21808917f..9ddeee6bd 100644 --- a/doc/source/devref/upgrade.rst +++ b/doc/source/devref/upgrade.rst @@ -149,7 +149,7 @@ To provide better compatibility guarantees for rolling upgrades, RPC interfaces could also define specific format for arguments they accept. In OpenStack world, it's usually implemented using oslo.versionedobjects library, and relying on the library to define serialized form for arguments that are passed -thru AMQP wire. +through AMQP wire. Note that Neutron has *not* adopted oslo.versionedobjects library for its RPC interfaces yet (except for QoS feature). diff --git a/doc/source/policies/blueprints.rst b/doc/source/policies/blueprints.rst index 219557f6d..d328856e5 100644 --- a/doc/source/policies/blueprints.rst +++ b/doc/source/policies/blueprints.rst @@ -134,7 +134,7 @@ The workflow for the life an RFE in Launchpad is as follows: * Escalate issues, and raise warnings to the release team/PTL if the effort shows slow progress. Approver and assignee are key parts to land a blueprint: should the approver and/or assignee be unable to continue - the committment during the release cycle, it is the Approver's + the commitment during the release cycle, it is the Approver's responsibility to reach out the release team/PTL so that replacements can be identified. * Provide a status update during the Neutron IRC meeting, if required.