From a7df10146a398a2d5cdc9ef49710317fa7838845 Mon Sep 17 00:00:00 2001 From: Ngo Quoc Cuong Date: Sat, 6 May 2017 00:02:18 +0700 Subject: [PATCH] Trivial fix typos while reading doc Change-Id: I704a176664fd7a980309d7ff7a5021b1e4c4b033 --- doc/source/devref/images/live-mig-ovs-hybrid.txt | 2 +- doc/source/devref/images/live-mig.txt | 2 +- doc/source/devref/policy.rst | 2 +- doc/source/policies/bugs.rst | 4 ++-- doc/source/policies/release-checklist.rst | 2 +- doc/source/stadium/governance.rst | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/source/devref/images/live-mig-ovs-hybrid.txt b/doc/source/devref/images/live-mig-ovs-hybrid.txt index 95e8951b159..2b9350adba0 100644 --- a/doc/source/devref/images/live-mig-ovs-hybrid.txt +++ b/doc/source/devref/images/live-mig-ovs-hybrid.txt @@ -82,7 +82,7 @@ note over nova_compute1, nova_compute2 end note note left of nova_compute1 live migration - succeded + succeeded end note nova_compute1 -> nova_compute1 : post_live_migration diff --git a/doc/source/devref/images/live-mig.txt b/doc/source/devref/images/live-mig.txt index d7a6e587470..bd42f17227e 100644 --- a/doc/source/devref/images/live-mig.txt +++ b/doc/source/devref/images/live-mig.txt @@ -107,7 +107,7 @@ end note left of nova_compute1 live migration - succeded + succeeded end note nova_compute1 -> nova_compute1 : post_live_migration diff --git a/doc/source/devref/policy.rst b/doc/source/devref/policy.rst index f30311d6974..c50b69b698c 100644 --- a/doc/source/devref/policy.rst +++ b/doc/source/devref/policy.rst @@ -256,7 +256,7 @@ served by Neutron "core" and for the APIs served by the various Neutron * There is still only one check which is hardcoded in Neutron's API layer: the check to verify that a project owns the network on which it is creating a port. This check is hardcoded and is always executed when creating a - port, unless the network is shared. Unfortunatelu a solution for performing + port, unless the network is shared. Unfortunately a solution for performing this check in an efficient way through the policy engine has not yet been found. Due to its nature, there is no way to override this check using the policy engine. diff --git a/doc/source/policies/bugs.rst b/doc/source/policies/bugs.rst index 5e34eac6ff2..79628753b9f 100644 --- a/doc/source/policies/bugs.rst +++ b/doc/source/policies/bugs.rst @@ -228,7 +228,7 @@ The process of bug triaging consists of the following steps: * Check if a bug was filed for a correct component (project). If not, either change the project or mark it as "Invalid". -* For bugs that affect documenation (including autogenerated DocImpact bugs) +* For bugs that affect documentation (including autogenerated DocImpact bugs) proceed like this. If documentation affects * the ReST API, add "openstack-api-site" to the affected projects. @@ -297,7 +297,7 @@ Check for Bugs with the 'timeout-abandon' tag: * Search for any bugs with the timeout abandon tag: `Timeout abandon `_. This tag indicates that the bug had a patch associated with it that was - automatically abandonded after a timing out with negative feedback. + automatically abandoned after a timing out with negative feedback. * For each bug with this tag, determine if the bug is still valid and update the status accordingly. For example, if another patch fixed the bug, ensure it's marked as 'Fix Released'. Or, if that was the only patch for the bug and diff --git a/doc/source/policies/release-checklist.rst b/doc/source/policies/release-checklist.rst index ea9551b98f2..df646a82f54 100644 --- a/doc/source/policies/release-checklist.rst +++ b/doc/source/policies/release-checklist.rst @@ -47,7 +47,7 @@ New major release process contains several phases: #. at this point, master branch is open for patches targeted to the next release; PTL unblocks all patches that were blocked in step 1; #. if additional patches are identified that are critical for the release and - must be shipped in the final major build, correpsponding bugs are tagged + must be shipped in the final major build, corresponding bugs are tagged with -rc-potential in Launchpad, fixes are prepared and land in master branch, and are then backported to the newly created stable branch; #. if patches landed in the release stable branch as per the previous step, a diff --git a/doc/source/stadium/governance.rst b/doc/source/stadium/governance.rst index eacca14f183..2760c49f983 100644 --- a/doc/source/stadium/governance.rst +++ b/doc/source/stadium/governance.rst @@ -245,7 +245,7 @@ Checklist The `neutron-lib patch `_ introduces the elements that define the API, and testing coverage validates that the resource and actions maps use valid keywords. - API reference documention is provided alongside the definition to + API reference documentation is provided alongside the definition to keep everything in one place. The `neutron patch `_ uses the Neutron extension framework to plug the API definition