openstack/i18n
Code Issues Proposed changes

Fix typos and translation builds

Browse Source 
We sometimes received random non-throughout typo fixes,
so it would be helpful to check typos throughoutly.

Co-Authored-By: Frank Kloeker <f.kloeker@telekom.de>

Change-Id: Ib4727ea7e48b3c6153b01b2a5572efcb3f054a4e
This commit is contained in:
Akihiro Motoki 2019-01-18 07:14:41 +09:00 committed by Frank Kloeker
parent 8c6bb12c2c
commit 16aadf6924
5 changed files with 7 additions and 5 deletions

2
doc/source/about.rst

@ -37,7 +37,7 @@ The convention for heading levels is as follows::
Heading 3
~~~~~~~~~
Underline with tildas for heading 3 sections.
Underline with tildes for heading 3 sections.
Translation
-----------

4
doc/source/infra.rst

@ -19,7 +19,7 @@ the repositories.
The first job is for Zanata-side updates. Up-to-date source strings to be
translated are compared and updated between OpenStack project repositories
and Zanata. If source texts in OpenStack project repositories are changed,
then change sets are pushed into Zanata so translaters deal with up-to-date
then change sets are pushed into Zanata so translators deal with up-to-date
source strings.
On the other hand, the second job is aimed to reflect changes in translated
strings in Zanata (after translators do translation activities) into
@ -41,7 +41,7 @@ get removed, there is also a lower threshold for releases of **66
percent** of messages translated as policy - which is only manually
enforced.
The OpenStack infra scripts excuted by tasks currently download new files that
The OpenStack infra scripts executed by tasks currently download new files that
are at least **75 percent** translated and if files grow over time but do not
get new translations (or strings change too much), they will be
removed again automatically from the project with a lower threshold of

2
doc/source/release_management.rst

@ -94,7 +94,7 @@ Documentation projects
All upstream OpenStack documents in ``openstack-manuals`` and project
repositories use ``master`` branch and can have stable branches depending
on release models and maintaining documents in different project teams.
Cross-project liaisons are strongly encouraged to communiticate with I18n
Cross-project liaisons are strongly encouraged to communicate with I18n
team so that I18n team can discuss and decide which stable documents are
the target in I18n team and when translators start to translate stable
documents.

2
playbooks/README.rst

@ -2,7 +2,7 @@ Ansible playbooks for I18n maintenance
======================================
This folder contains Ansible playbooks for maintenance I18n work.
Typically the playbooks are running localy on user's workstation.
Typically the playbooks are running locally on user's workstation.
Ansible >= 2.2.0.0 is required to work with json_query.
Usage: "ansible-playbook <playbook.yml>"

2
tox.ini

@ -23,6 +23,8 @@ commands = {posargs}
commands = {posargs}
[testenv:docs]
setenv =
SPHINX_WARNINGS_TRANS=1
commands =
doc8 doc/source
# Build translated guides