Fixed Latin words, replaced all via with either through or by (#79004) (#79068)

(cherry picked from commit 4f4ad453c4)

Co-authored-by: Ishan Siddiqui <77967215+ishan-siddiqui@users.noreply.github.com>

docs/docsite/rst/network/user_guide/platform_cnos.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -59,7 +59,7 @@ Example CLI ``group_vars/cnos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_dellos10.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       through a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -60,7 +60,7 @@ Example CLI ``group_vars/dellos10.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_dellos6.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       through a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -59,7 +59,7 @@ Example CLI ``group_vars/dellos6.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_dellos9.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       through a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -59,7 +59,7 @@ Example CLI ``group_vars/dellos9.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_enos.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -61,7 +61,7 @@ Example CLI ``group_vars/enos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_eos.rst

@@ -24,7 +24,7 @@ Connections available
                                                                       present
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)                   via a web proxy
+    Indirect Access       by a bastion (jump host)                    through a web proxy
 
     Connection Settings   ``ansible_connection:``                     ``ansible_connection:``
                           ``ansible.netcommon.network_cli``           ``ansible.netcommon.httpapi``
@@ -64,7 +64,7 @@ Example CLI ``group_vars/eos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_eric_eccli.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -54,7 +54,7 @@ Example CLI ``group_vars/eric_eccli.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_exos.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)                   via a web proxy
+    Indirect Access       by a bastion (jump host)                    through a web proxy
 
     Connection Settings   ``ansible_connection:``                     ``ansible_connection:``
                             ``ansible.netcommon.network_cli``           ``ansible.netcommon.httpapi``
@@ -56,7 +56,7 @@ Example CLI ``group_vars/exos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_frr.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -53,7 +53,7 @@ Example CLI ``group_vars/frr.yml``
 - The ``ansible_user`` should be a part of the ``frrvty`` group and should have the default shell set to ``/bin/vtysh``.
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_icx.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -57,7 +57,7 @@ Example CLI ``group_vars/icx.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_ios.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -59,7 +59,7 @@ Example CLI ``group_vars/ios.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_iosxr.rst

@@ -28,7 +28,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password  accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)                   via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)                    by a bastion (jump host)
 
     Connection Settings   ``ansible_connection:``                     ``ansible_connection:``
                             ``ansible.netcommon.network_cli``          ``ansible.netcommon.netconf``  
@@ -61,7 +61,7 @@ Example CLI inventory ``[iosxr:vars]``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_ironware.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -60,7 +60,7 @@ Example CLI ``group_vars/mlx.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_junos.rst

@@ -27,7 +27,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password  accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)                   via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)                    by a bastion (jump host)
 
     Connection Settings   ``ansible_connection:                       ``ansible_connection:
                           ``ansible.netcommon.network_cli``           ``ansible.netcommon.netconf``
@@ -62,7 +62,7 @@ Example CLI inventory ``[junos:vars]``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------
@@ -86,7 +86,7 @@ Before you can use NETCONF to connect to a switch, you must:
 - install the ``ncclient`` python package on your control node(s) with ``pip install ncclient``
 - enable NETCONF on the Junos OS device(s)
 
-To enable NETCONF on a new switch via Ansible, use the ``junipernetworks.junos.junos_netconf`` module through the CLI connection. Set up your platform-level variables just like in the CLI example above, then run a playbook task like this:
+To enable NETCONF on a new switch through Ansible, use the ``junipernetworks.junos.junos_netconf`` module through the CLI connection. Set up your platform-level variables just like in the CLI example above, then run a playbook task like this:
 
 .. code-block:: yaml
 

docs/docsite/rst/network/user_guide/platform_netconf_enabled.rst

@@ -26,7 +26,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       through a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.netconf``
     ====================  ==========================================
@@ -45,7 +45,7 @@ Before you can use NETCONF to connect to a switch, you must:
 - install the ``ncclient`` Python package on your control node(s) with ``pip install ncclient``
 - enable NETCONF on the Junos OS device(s)
 
-To enable NETCONF on a new switch via Ansible, use the platform specific module via the CLI connection or set it manually.
+To enable NETCONF on a new switch through Ansible, use the platform specific module through the CLI connection or set it manually.
 For example set up your platform-level variables just like in the CLI example above, then run a playbook task like this:
 
 .. code-block:: yaml

docs/docsite/rst/network/user_guide/platform_netvisor.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -55,7 +55,7 @@ Example CLI ``group_vars/netvisor.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_nos.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: community.netcommon.network_cli``
 
@@ -55,7 +55,7 @@ Example CLI ``group_vars/nos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_nxos.rst

@@ -24,7 +24,7 @@ Connections available
                                                                       present
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)                   via a web proxy
+    Indirect Access       by a bastion (jump host)                    by a web proxy
 
     Connection Settings   ``ansible_connection:``                     ``ansible_connection:``
                             ``ansible.netcommon.network_cli``             ``ansible.netcommon.httpapi``
@@ -61,7 +61,7 @@ Example CLI ``group_vars/nxos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------
@@ -82,7 +82,7 @@ Using NX-API in Ansible
 Enabling NX-API
 ---------------
 
-Before you can use NX-API to connect to a switch, you must enable NX-API. To enable NX-API on a new switch via Ansible, use the ``nxos_nxapi`` module via the CLI connection. Set up group_vars/nxos.yml just like in the CLI example above, then run a playbook task like this:
+Before you can use NX-API to connect to a switch, you must enable NX-API. To enable NX-API on a new switch through Ansible, use the ``nxos_nxapi`` module through the CLI connection. Set up group_vars/nxos.yml just like in the CLI example above, then run a playbook task like this:
 
 .. code-block:: yaml
 

docs/docsite/rst/network/user_guide/platform_routeros.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.network.network_cli``
 
@@ -59,7 +59,7 @@ Example CLI ``group_vars/routeros.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 - If you are getting timeout errors you may want to add ``+cet1024w`` suffix to your username which will disable console colors, enable "dumb" mode, tell RouterOS not to try detecting terminal capabilities and set terminal width to 1024 columns. See article `Console login process <https://wiki.mikrotik.com/wiki/Manual:Console_login_process>`_ in MikroTik wiki for more information.
 
 Example CLI task

docs/docsite/rst/network/user_guide/platform_slxos.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -56,7 +56,7 @@ Example CLI ``group_vars/slxos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_voss.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -59,7 +59,7 @@ Example CLI ``group_vars/voss.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_vyos.rst

@@ -24,7 +24,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: ansible.netcommon.network_cli``
 
@@ -55,7 +55,7 @@ Example CLI ``group_vars/vyos.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------

docs/docsite/rst/network/user_guide/platform_weos4.rst

@@ -25,7 +25,7 @@ Connections available
 
                           accepts ``-u myuser -k`` if using password
 
-    Indirect Access       via a bastion (jump host)
+    Indirect Access       by a bastion (jump host)
 
     Connection Settings   ``ansible_connection: community.netcommon.network_cli``
 
@@ -55,7 +55,7 @@ Example CLI ``group_vars/weos4.yml``
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration.
 - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration.
-- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables.
+- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables.
 
 Example CLI task
 ----------------