No latin terms (#79009)

Fixes #79006

4 files changed, 4 insertions, 4 deletions

diff --git a/docs/docsite/rst/playbook_guide/playbooks_intro.rst b/docs/docsite/rst/playbook_guide/playbooks_intro.rst
index 75be4e8322e..8592b0429ff 100644
--- a/docs/docsite/rst/playbook_guide/playbooks_intro.rst
+++ b/docs/docsite/rst/playbook_guide/playbooks_intro.rst
@@ -116,7 +116,7 @@ Assuming you load balance your checkout location, ``ansible-pull`` scales essent
 
 Run ``ansible-pull --help`` for details.
 
-There's also a `clever playbook <https://github.com/ansible/ansible-examples/blob/master/language_features/ansible_pull.yml>`_ available to configure ``ansible-pull`` via a crontab from push mode.
+There's also a `clever playbook <https://github.com/ansible/ansible-examples/blob/master/language_features/ansible_pull.yml>`_ available to configure ``ansible-pull`` through a crontab from push mode.
 
 Verifying playbooks
 ===================
diff --git a/docs/docsite/rst/playbook_guide/playbooks_loops.rst b/docs/docsite/rst/playbook_guide/playbooks_loops.rst
index 73d5a8a51c7..5e8afdeafb9 100644
--- a/docs/docsite/rst/playbook_guide/playbooks_loops.rst
+++ b/docs/docsite/rst/playbook_guide/playbooks_loops.rst
@@ -468,7 +468,7 @@ Accessing the name of your loop_var
 
 As of Ansible 2.8 you can get the name of the value provided to ``loop_control.loop_var`` using the ``ansible_loop_var`` variable
 
-For role authors, writing roles that allow loops, instead of dictating the required ``loop_var`` value, you can gather the value via the following
+For role authors, writing roles that allow loops, instead of dictating the required ``loop_var`` value, you can gather the value through the following
 
 .. code-block:: yaml+jinja
 
diff --git a/docs/docsite/rst/playbook_guide/playbooks_python_version.rst b/docs/docsite/rst/playbook_guide/playbooks_python_version.rst
index efcadb229cc..ee18b60713e 100644
--- a/docs/docsite/rst/playbook_guide/playbooks_python_version.rst
+++ b/docs/docsite/rst/playbook_guide/playbooks_python_version.rst
@@ -16,7 +16,7 @@ Dictionary views
 ================
 
 In Python2, the :meth:`dict.keys`, :meth:`dict.values`, and :meth:`dict.items`
-methods return a list.  Jinja2 returns that to Ansible via a string
+methods return a list.  Jinja2 returns that to Ansible using a string
 representation that Ansible can turn back into a list.
 
 In Python3, those methods return a :ref:`dictionary view <python3:dict-views>` object. The
diff --git a/docs/docsite/rst/playbook_guide/playbooks_reuse.rst b/docs/docsite/rst/playbook_guide/playbooks_reuse.rst
index 3731351774d..89cc5a42161 100644
--- a/docs/docsite/rst/playbook_guide/playbooks_reuse.rst
+++ b/docs/docsite/rst/playbook_guide/playbooks_reuse.rst
@@ -17,7 +17,7 @@ Ansible offers four distributed, re-usable artifacts: variables files, task file
   - A variables file contains only variables.
   - A task file contains only tasks.
   - A playbook contains at least one play, and may contain variables, tasks, and other content. You can re-use tightly focused playbooks, but you can only re-use them statically, not dynamically.
-  - A role contains a set of related tasks, variables, defaults, handlers, and even modules or other plugins in a defined file-tree. Unlike variables files, task files, or playbooks, roles can be easily uploaded and shared via Ansible Galaxy. See :ref:`playbooks_reuse_roles` for details about creating and using roles.
+  - A role contains a set of related tasks, variables, defaults, handlers, and even modules or other plugins in a defined file-tree. Unlike variables files, task files, or playbooks, roles can be easily uploaded and shared through Ansible Galaxy. See :ref:`playbooks_reuse_roles` for details about creating and using roles.
 
 .. versionadded:: 2.4