openstack/training-guides
Code Issues Proposed changes

[upstream] Fix typos

Browse Source 
I found several typos during translations.
This commit fixes them.

Change-Id: I9f155fd5a6c0a1523332eebd559f6deee184b56a
This commit is contained in:
Akihiro Motoki 2016-10-05 23:56:18 +09:00
parent 5e0f091688
commit 994dec43d6
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/upstream-training/README.rst
View File

@ -15,7 +15,7 @@ Install tox using pip::
Build the presentation
----------------------
Build the presention using tox::
Build the presentation using tox::
tox -e upstream-slides

4
doc/upstream-training/irc.rst
View File

@ -9,12 +9,12 @@ Install an IRC Program
----------------------
We'll install an IRC program called Hexchat.
For a linux distrubtions like Debian, Ubuntu, or Mint open a terminal and
For a linux distributions like Debian, Ubuntu, or Mint open a terminal and
type::
sudo apt install hexchat
For a linux distrubtions like Redhat, Fedora 21 or earlier, or Centos open
For a linux distributions like Redhat, Fedora 21 or earlier, or CentOS open
a terminal and type::
sudo yum install hexchat

2
doc/upstream-training/source/00-01-openstack-as-software.rst
View File

@ -45,7 +45,7 @@ OpenStack from Telecom/NFV perspective
OpenStack from Telecom/NFV perspective
======================================
- Virtual Infrastructure Manager (VIM) + NFV Infratsructure (NFVI)
- Virtual Infrastructure Manager (VIM) + NFV Infrastructure (NFVI)
- Most of the OpenStack services

2
doc/upstream-training/source/03-technical-committee.rst
View File

@ -63,7 +63,7 @@ bug tracker, etc) and coordinated *processes* to produce a number of
OpenStack's mission.
- Teams in OpenStack can be freely created as they are needed
- Teams of official projects are under the authority of the Technical Commitee
- Teams of official projects are under the authority of the Technical Committee
- The official list of projects:
- http://governance.openstack.org/reference/projects/

2
doc/upstream-training/source/04-official-openstack-projects.rst
View File

@ -23,7 +23,7 @@ Official OpenStack projects
Benefits of being an Official OpenStack project
===============================================
- Contributors get to vote in the Technical Commitee election
- Contributors get to vote in the Technical Committee election
- Can publish to docs.openstack.org and developer.openstack.org
- The teams get space on OpenStack Summits and Project Team Gatherings (PTG)
- Get marketing from the OpenStack Foundation

2
doc/upstream-training/source/17-commit-message.rst
View File

@ -41,7 +41,7 @@ Contents of a Commit Message (Body)
===================================
- Lines limited to 72 characters
- Explaination of issue being solved and why it should be fixed
- Explanation of issue being solved and why it should be fixed
- Explain how problem is solved
- Other possible content
- Does it improve code structure?

2
doc/upstream-training/upstream-details.rst
View File

@ -273,7 +273,7 @@ These slides prepare students for the Lego activity, and ensure they
understand the metaphors in use. The Lego in the exercise represents the
code of a software project, in this case OpenStack. The students all take
on roles that represent various facets of the OpenStack community, including
upstream roles like Foundation and TCT, and contributors like corporations,
upstream roles like Foundation and TC, and contributors like corporations,
and unaffiliated individuals animated by unknown motives (free agents).
The group is split into their new 'teams' at this stage. Facilitators can