diff --git a/doc/source/about.rst b/doc/source/about.rst
index c3fd8f5..5b3b677 100644
--- a/doc/source/about.rst
+++ b/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
 -----------
diff --git a/doc/source/infra.rst b/doc/source/infra.rst
index 4506b15..68554d2 100644
--- a/doc/source/infra.rst
+++ b/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
diff --git a/doc/source/release_management.rst b/doc/source/release_management.rst
index af859ce..476c9e9 100644
--- a/doc/source/release_management.rst
+++ b/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.
diff --git a/playbooks/README.rst b/playbooks/README.rst
index 7fd92e6..0558f1a 100644
--- a/playbooks/README.rst
+++ b/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>"
diff --git a/tox.ini b/tox.ini
index 119f59f..c39e658 100644
--- a/tox.ini
+++ b/tox.ini
@@ -23,6 +23,8 @@ commands = {posargs}
 commands = {posargs}
 
 [testenv:docs]
+setenv =
+  SPHINX_WARNINGS_TRANS=1
 commands =
   doc8 doc/source
   # Build translated guides