openstack
/
openstack-manuals
Code Issues Proposed changes

Edited word choice for conciseness 

Edited words and grammar for clarity

Change-Id: I76826fb8c0d345d1d5f1fea9fd19478e8338ec5b
This commit is contained in:
“devon 2016-02-04 14:59:38 -05:00
parent bde9250702
commit ac7fa64128
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/contributor-guide/source/first-timers-quickstart.rst
View File

@ -21,7 +21,7 @@ Other good first-time documentation tasks are bug triaging and bug fixing:
#. If you are up for it, assign the bug to yourself after it has been
confirmed by one other person. Fix it by committing the required changes
to the OpenStack documentation.
to OpenStack documentation.
The following diagram shows the basic setup workflow:

6
doc/contributor-guide/source/rst-conv.rst
View File

@ -7,10 +7,10 @@ RST formatting conventions
OpenStack documentation uses reStructuredText (RST) markup syntax
with Sphinx extensions.
RST is a powerful and straightforward markup language, that in combination
RST is a powerful and straightforward markup language that, in combination
with Sphinx, provides a wide range of facilities for intelligent and
good-looking documentation creation. It uses simple and implicit
syntax to introduce a wide range of content elements, such as, titles,
appealing documentation creation. It uses simple and implicit
syntax to introduce a variety of content elements such as titles,
code blocks, vertical lists, and many others. All the source content formatted
using RST is stored in files with the ``.rst`` extension.