openstack
/
i18n
Code Issues Proposed changes

Fix some typos and grammar errors 

TrivialFix

Change-Id: Ia2a569514c27ccd9b7dbb925dca256ed07843d8e
This commit is contained in:
melissaml 2016-10-16 15:51:36 +08:00
parent 9af883be8a
commit 0ddbf4e9fe
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/check_translation.rst
View File

@ -74,9 +74,9 @@ Running DevStack
Another convenient way is to check dashboard translations is to run DevStack in
your local environment. To run DevStack, you need to prepare ``local.conf``
file, but no worries. Several ``local.conf`` files are shared on the Internet
and an minimum example is shown below. From our experience, you need a machine
and a minimum example is shown below. From our experience, you need a machine
with two or four CPU cores, 8 GB memory and 20 GB disk to run DevStack
comfortablely. If you enable just major OpenStack projects, the machine
comfortably. If you enable just major OpenStack projects, the machine
requirement would be much smaller like 2~4GB memory.
.. code-block:: console
@ -117,7 +117,7 @@ Replace ``$BRANCH`` with an appropriate branch such as ``master``,
.. literalinclude:: ../../checksite/horizon-reload.sh
:language: bash
Another way is to rerun DevStack. Ensure to include ``RECLONE=True`` in
The other way is to rerun DevStack. Ensure to include ``RECLONE=True`` in
your ``local.conf`` before running ``stack.sh`` again so that DevStack
retrieve the latest codes of horizon and other projects.

4
doc/source/glossary.rst
View File

@ -10,7 +10,7 @@ Glossary of your language
A glossary file of your language is found at
``i18n/locale/<lang>/LC_MESSAGES/i18n.po`` in the i18n repository.
The file is an usual PO file.
The file is a usual PO file.
When you want to update a glossary of your language,
edit a corresponding glossary file using your favorite editor and
@ -19,7 +19,7 @@ propose a change to the Gerrit review system.
Once your change is merged, the updated glossary will be uploaded
to Zanata. Note that the upload to Zanata is a **manual** process now.
Only the Zanata administrator (usually the i18n PTL and some limited folks)
can upload an glossary. If your glossary is not uploaded, contact the i18n team
can upload a glossary. If your glossary is not uploaded, contact the i18n team
or the PTL via the i18n mailing list.
.. note::