Merge pull request #718 from ehassman-g/typo_fixes

Documentation typo fixes

Author: flit

docs/DEVELOPERS-GUIDE.md

@@ -133,7 +133,7 @@ There are three defined ways in which DAPLink can be extended. These are adding
 DAPLink has an extensive set of automated tests written in Python. They are used for regression testing, but you can use them to validate your DAPLink port. Details are [here](AUTOMATED_TESTS.md)
 
 An option to search for the daplink firmware build in uvision and mbedcli build folders.
-`python test/run_test.py --projecttool mbedcli ...` or `python test/run_test.py --projecttool uvision ...`.
+`python test/run_test.py --project-tool mbedcli ...` or `python test/run_test.py --project-tool uvision ...`.
 
 ## Release
 

docs/PORT_BOARD.md

@@ -107,7 +107,7 @@ You may need to update one or more other dictionaries. See comments in the code
 See [Automated Tests](AUTOMATED_TESTS.md) for more information related to automated testing.
 
 # Post-build Board ID and Family ID
-Board ID and Family ID can be overwritten by `tools/post_build_scpript.py`. This is helpful for supporting existing families and adding board IDs to the database without the need to compile DAPLink. Board ID can uniquely identify the target board while family ID can select which target family to support.
+Board ID and Family ID can be overwritten by `tools/post_build_script.py`. This is helpful for supporting existing families and adding board IDs to the database without the need to compile DAPLink. Board ID can uniquely identify the target board while family ID can select which target family to support.
 ```
 usage: post_build_script.py [-h] [--board-id BOARD_ID] [--family-id FAMILY_ID]
                             [--bin-offset BIN_OFFSET]