Spell fix

docs/ide/cloud9.rst

@@ -26,7 +26,7 @@ server output, and Run apps easily with the built-in Terminal and Runners.
 
     1. Please make sure to read :ref:`pio_remote` guide first.
     2. You need :ref:`cmd_account` if you don't have it. Registration is FREE.
-    3. You should have a run :ref:`cmd_remote_agent` on a local host machine
+    3. You should have a run :ref:`cmd_remote_agent` on a host machine
        where hardware devices are connected or visible for remote operations.
 
 Demo

docs/ide/codeanywhere.rst

@@ -28,7 +28,7 @@ development more productive and fun.
 
     1. Please make sure to read :ref:`pio_remote` guide first.
     2. You need :ref:`cmd_account` if you don't have it. Registration is FREE.
-    3. You should have a run :ref:`cmd_remote_agent` on a local host machine
+    3. You should have a run :ref:`cmd_remote_agent` on a host machine
        where hardware devices are connected or visible for remote operations.
 
 Demo

docs/plus/pio-remote.rst

@@ -67,9 +67,9 @@ This approach allows to work with distributed hardware located in the different
 places, networks, etc.
 
 This technology allows to work with remote devices in generic form as you
-do that with local devices using PlatformIO ecosystem. The only one difference
+do that with host devices using PlatformIO ecosystem. The only one difference
 is a prefix "remote" before each generic PlatformIO command. For example,
-listing of local and remote devices will look like :ref:`cmd_device_list` and
+listing of host and remote devices will look like :ref:`cmd_device_list` and
 :ref:`cmd_remote_device_list`.
 
 Quick Start

docs/plus/unit-testing.rst

@@ -43,7 +43,7 @@ Desktop
 
 PlatformIO wraps test and main program (from :ref:`projectconf_pio_src_dir`)
 with own |PIOUTF|, builds final program using :ref:`platform_native` and run
-test on a local host machine (desktop).
+test on a host machine (desktop).
 
 .. note::
     PlatformIO does not install any toolchains automatically for
@@ -58,7 +58,7 @@ PlatformIO wraps test and main firmware (from :ref:`projectconf_pio_src_dir`)
 with own |PIOUTF|, builds special firmware for a target device and upload it.
 After uploading, PlatformIO connects to embedded device (board) using
 :ref:`projectconf_test_port` , starts test, collects results and shows test
-results on the local host machine.
+results on the host machine.
 
 Currently, |PIOUTE| supports these embedded frameworks:
 
@@ -82,7 +82,7 @@ from :ref:`projectconf`.
 
 Local
 ~~~~~
-Allows to run tests on local host machine or on the target devices (boards)
+Allows to run tests on host machine or on the target devices (boards)
 that are directly connected to this machine. In this case, need to use
 :ref:`cmd_test` command.
 

docs/userguide/remote/cmd_agent.rst

@@ -14,7 +14,7 @@
 PIO Remote™ Agent
 =================
 
-Start :ref:`cmd_remote_agent` on a local host machine and work remotely with
+Start :ref:`cmd_remote_agent` on a host machine and work remotely with
 your devices **WITHOUT** extra software, services, SSH, VPN, tunneling or
 opening incoming network ports.