Readme and help fixes

Author: Jarno Lamsa

TEST_APPS/readme.md

@@ -42,15 +42,15 @@ Some devices may offer multiple network interfaces to operate with. For example,
 The tests can be run for either one of those using already existing test-config -files.
 
 To run the tests with Wi-Fi interface:
-`>mbed test -m UBLOX_EVK_ODIN_W2 -t <toolchain> --icetea --test-config tools/test-configs/HeapBlockDeviceAndWifiInterface.json.json`
+`>mbed test -m UBLOX_EVK_ODIN_W2 -t <toolchain> --icetea --test-config tools/test-configs/HeapBlockDeviceAndWifiInterface.json`
 
 To run the tests with ethernet interface:
 `>mbed test -m UBLOX_EVK_ODIN_W2 -t <toolchain> --icetea --test-config tools/test-configs/HeapBlockDeviceAndEthernetInterface.json`
 
 #### Providing Wi-Fi access point information
 
 If you are using Wi-Fi interface for running the tests, you need to provide also information about the used access point.
-The information can be provided in the used test-config -file.
+The information can be provided in the used test-config file.
 
 Example of access point information:
 ```
@@ -89,5 +89,5 @@ Icetea prints the results from the test run to the command line, and the final r
 +---------------+----------------+
 ```
 
-The results from the tests can also be found from mbed-os/log folder.
+The results from the tests can also be found in the mbed-os/log folder.
 You probably want to add the log folder to your .mbedignore file to prevent issues with build commands becoming too long over the time.

tools/run_icetea.py

@@ -249,7 +249,7 @@ def load_build_data(build_data_path):
                             action='store_true',
                             dest='application_list',
                             default=False,
-                            help='List application that need to be build')
+                            help='List applications that need to be build')
 
         parser.add_argument('--ignore-checks',
                             action='store_true',