Cleaning up duplications

Author: iriark01

docs/porting/porting_full_process/porting_reqs.md

@@ -4,11 +4,16 @@
 
 Porting Mbed OS requires the following hardware:
 
-- An evaluation board with the targeted MCU.
+- A development PC. You can port targets, connectivity and storage on Windows, macOS or Linux. However, due to limitations in some development tools that Mbed OS uses, you need a Windows PC for DAPLink/FlashAlgo development.
+
+-  An evaluation board with a target MCU, debug probe or an integrated interface chip. The hardware [is reviewed in greater details later in this document]().
 
     The new target needs a unique board ID. [Contact Arm]() to get one.
 
-- A micro USB cables. One Micro USB cable connects the evaluation board to your development PC.
+- A storage device (SD or external flash).
+- A micro SD card for the CI test shield.<!--are these the same thing?-->
+
+- A micro USB cable to connect the evaluation board to your development PC.
 
 You may also need:
 
@@ -19,7 +24,6 @@ You may also need:
 The following items might help you test SPI, I2C and Pins:
 
 - A CI test shield v2.0.0. For details, refer to [https://github.com/ARMmbed/ci-test-shield](https://github.com/ARMmbed/ci-test-shield).
-- A micro SD card for the CI test shield.
 
 <span class="tips">Check the user guide of the evaluation board to see if anything needs to be done prior to using a debug probe and running Mbed OS programs.</span>
 
@@ -30,10 +34,13 @@ Please install the following:
 - [Python 2.7](https://www.python.org/downloads/release/python-2715/).
 - [Git](https://git-scm.com/downloads).
 - [Mbed CLI](../tools/installation-and-setup.html).
+- Choose an IDE and debugger. The three commonly used IDEs are [Eclipse](https://www.eclipse.org/ide/), [IAR Embedded Workbench](https://www.iar.com/iar-embedded-workbench/) and [Keil MDK](http://www.keil.com/).
+
+    Limitations:
+
+    - Eclipse is license free, whereas both IAR and Keil IDE require licenses.
+    - Currently, DAPLink development works only Keil MDK. You will have to use Keil for pyOCD and DAPLink development.
+
 - (Optional) [FTDI serial driver](http://www.ftdichip.com/Drivers/VCP.htm).
-- Toolchains:
-   - [GNU Arm Embedded Toolchain (GCC)](https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads).
-   - [IAR](https://www.iar.com/iar-embedded-workbench/).
-   - [Arm Compiler 5 or 6](https://developer.arm.com/products/software-development-tools/compilers/arm-compiler/downloads/version-5).
 
 <span class="notes">The [tools documentation](../tools/index.html) contains the exact third party tool versions supported in a specific Mbed OS release.</span>

docs/porting/porting_full_process/porting_start.md

@@ -1,36 +1,26 @@
 ## Porting guide
 
-This document provides guidelines for adding a new MCU target to Mbed OS and Pelion.
+This document provides guidelines for adding a new MCU target to Mbed OS and the Pelion IoT Platform.
 
 ### Scope and milestones
-<!--I'm not sure I see how these milestones follow what's below, at least in numbering-->
-The following milestones usually need to happen to port Mbed OS to a board or target:
 
-1. Set up a development environment. Please choose:
-   - Your primary development PC (Windows, Mac OS or Linux).
+You will usually need to go through all of these steps to port Mbed OS:
 
-       You can port targets, connectivity and storage on Windows, macOS or Linux. Due to limitations in some development tools that Mbed OS uses, you need a Windows PC for DAPLink/FlashAlgo development.
-
-  - An evaluation board with a target MCU, debug probe or an integrated interface chip.<!--I'm guessing the "or" is only for the last two things - debug probe or interface chip. In which case, this sentence requires rewriting.--> The hardware [is reviewed in greater details later in this document]().
-  - A storage device (SD or external flash).
+1. Set up a development environment (including IDE and debugger) and your target.
 
 1. Locate reusable code to port to Mbed OS.
 <!--Are the reusable code and SDK related? Are they the same thing?-->
     If there is an SDK available to speed up the porting process, we recommend reusing it (assuming copyright of the existing code is preserved).
 
-1. Choose an IDE and debugger. The three commonly used IDEs are [Eclipse](https://www.eclipse.org/ide/), [IAR Embedded Workbench](https://www.iar.com/iar-embedded-workbench/) and [Keil MDK](http://www.keil.com/).
-
-    Limitations:
+    <!--I actually don't quite understand this. Is it mandatory to find reusable code (which is implied in the first line), or is it "if you have it, use it"?-->
 
-    - Eclipse is license free, whereas both IAR and Keil IDE require licenses.
-    - Currently, DAPLink development works only Keil MDK. You will have to use Keil for pyOCD and DAPLink development.
 
 1. The [Mbed Enabled](https://www.mbed.com/en/about-mbed/mbed-enabled/introduction/) program requires pyOCD, so ultimately pyOCD needs to support the new target. To allow parallel development in porting targets, connectivity and storage while pyOCD is still under development, you can use other IDEs supported on the evaluation board in the beginning phase.
 
 1. Implement and test CMSIS pack, bootstrap, linker script and startup code.
 
 A basic framework is ready after this step. You can do the rest of the porting work in parallel:
 
-1. Implement and test porting APIs. This includes all components described in the rest of this porting guide.
+1. Implement and test porting APIs<!--we call the modules everywhere else-->. This porting guide provides the recommended porting order and links to full porting information about each module.
 
-1. Test Mbed OS and Pelion example applications (as listed [in the final steps in this porting guide]()). This steps verifies that your new port is fully functional.
+1. Test Mbed OS and Pelion example applications. This steps verifies that your new port is fully functional.