openinfra/interop
Code Issues Proposed changes

Fixing typos in the documentation

Browse Source 
While reading some of the documentation in the Interop Github repo
I found a few typos in the docs and thought I'd fix them upstream.

Change-Id: If7ff117e6634c1ceac19591d2b78844bd398681d
This commit is contained in:
Noor Muhammad Malik 2020-06-01 19:35:57 +05:00
parent 5a37e4d758
commit 0f4c804f88
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
HACKING.rst
View File

@ -145,13 +145,13 @@ To file a flag request for a test, follow these steps:
}
},
#. Once you've saved your changes, commit the chage locally:
#. Once you've saved your changes, commit the change locally:
.. code-block:: console
$ git commit -a
Be sure to write a useful commit message explaning your change.
Be sure to write a useful commit message explaining your change.
#. Push the change to gerrit, where your request can be reviewed:

8
doc/source/process/CoreDefinition.rst
View File

@ -9,7 +9,7 @@ The following list represents the "guiding principles" used by the
Foundation Board to determine how commercial implementations of OpenStack
can be granted use of the trademark. They will continue to get refined over
the next 6 months as the to-be-renamed-Core-Definition Committee refines
the must-pass test selection process and governance. They committee may
the must-pass test selection process and governance. The committee may
suggest changes to the by-laws to clarify the definition of core.
::
@ -43,7 +43,7 @@ Principles
2. We want to make sure that the OpenStack™ mark means something.
3. The OpenStack™ mark is not the same as the OpenStack brand; however,
the Board uses it’s control of the mark as a proxy to help manage the
the Board uses its control of the mark as a proxy to help manage the
brand.
2. Core is a subset of the whole project
@ -70,7 +70,7 @@ Principles
4. Claiming OpenStack requiring use of designated upstream code
1. Implementation’s claiming the OpenStack™ mark must use the OpenStack
1. Implementations claiming the OpenStack™ mark must use the OpenStack
upstream code (or be using code submitted to upstream)
2. You are not OpenStack, if you pass all the tests but do not use the
@ -83,7 +83,7 @@ Principles
community
5. This behavior improves interoperability because there is more shared
code between implementation
code between implementations
5. Projects must have an open reference implementation