openstack/governance
Code Issues Proposed changes

Typo fixes

Browse Source 
Noticed a few things that needed tidying.

Change-Id: I1addff2c309491e5c75d32465f738d7435b99b87
This commit is contained in:
Joshua Hesketh 2017-04-06 19:38:24 +10:00 committed by Steve Martinelli
parent 9c5143d658
commit 31a66b6200
5 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
reference/base-services.rst
View File

@ -21,7 +21,7 @@ Current list of base services
**An oslo.messaging-compatible message queue**
Some inter-process and inter-service communication in OpenStack
components is accomplished using message queues, through oslo.messaging
components is accomplished using message queues through oslo.messaging
as an indirection layer. While most OpenStack deployments use RabbitMQ,
other message queues are supported.

2
reference/charter.rst
View File

@ -107,7 +107,7 @@ and should be held open for no less than four business days.
Voters for PTL seats ("APC")
============================
Voters for a given project's PTL election are the active project contributors
Voters for a given project's PTL election are the Active Project Contributors
("APC"), which are a subset of the Foundation Individual Members. Individual
Members who committed a change to a repository of a project over the last two
6-month release cycles are considered APC for that project team.

2
reference/new-projects-requirements.rst
View File

@ -25,7 +25,7 @@ When considering new projects for addition, the TC will check that:
* The proposed project uses an open source license (preferably the Apache
v2.0 license, since it is necessary if the project wants to be used in
an OpenStack trademark program)
* Project must have no library dependencies which effectively restrict
* The project must have no library dependencies which effectively restrict
how the project may be distributed or deployed
* Open Community:

6
reference/principles.rst
View File

@ -17,8 +17,8 @@ One OpenStack
-------------
OpenStack is one community with one common mission, producing one framework
of collaborating components. Our organization into separate source code
repositories and teams allows contributors to focus on their areas of
of collaborating components. Our organization is split into separate source
code repositories and teams allowing contributors to focus on their areas of
interest and expertise, but does not make OpenStack a loose collection of
disconnected projects.
@ -69,7 +69,7 @@ OpenStack Leaders Exist to Serve Their Community
OpenStack leaders hold their positions only in order to serve the people
they lead. The TC only exists to serve the technical community. PTLs
exist to serve the contributors to and users of their projects.
exist to serve the contributors and users of their projects.
Changes in Leadership are Good
------------------------------

4
reference/service-project-naming.rst
View File

@ -30,7 +30,7 @@ the ``openstack`` CLI command.
The history of this decision is that the documentation contributors wanted the
least amount of cognitive overhead when writing and reviewing. Learning rules
about case can be difficult across multiple projects and with hundreds of
about case can be difficult across multiple projects with hundreds of
documentation contributors and thousands of changes and additions. Lowercase
for project names as a rule is then easiest to review and enforce at this scale
and growth pattern.
@ -74,5 +74,3 @@ Developer documentation may refer to the project name, but end-user, operator,
administrator, and application developer documentation must refer to the
service name. When reviewing service names, consider the consumers of the
information.