Edit bootloader.md

Copy edit for active voice and spelling, and remove duplicate section because we link to its duplicate.

Author: Amanda Butler

docs/tools/bootloader.md

@@ -1,6 +1,6 @@
 ## Bootloader configuration
 
-This page describes each bootloader configuration parameter in detail. For a guide on using the managed and unmanaged bootloader modes, please see [the bootloader turorial](/docs/v5.7/tutorials/bootloader.html).
+This page describes each bootloader configuration parameter in detail. For a guide on using the managed and unmanaged bootloader modes, please see [the bootloader tutorial](/docs/v5.7/tutorials/bootloader.html).
 
 There are 4 configuration parameters that affect the location of an application in ROM:
 
@@ -9,7 +9,7 @@ There are 4 configuration parameters that affect the location of an application
 - `target.bootloader_img`
 - `target.restrict_size`
 
-All of these parameters are valid in `targets.json`, `mbed_lib.json` and `mbed_app.json` and may be defined for individual targets and the wildcard target, `*`. A parameter in `mbed_lib.json` overrides a parameter in `targets.json`, and a parameter in `mbed_app.json` overrides one in `mbed_lib.json`.
+All of these parameters are valid in `targets.json`, `mbed_lib.json` and `mbed_app.json`. You may define them for individual targets and the wildcard target, `*`. A parameter in `mbed_lib.json` overrides a parameter in `targets.json`, and a parameter in `mbed_app.json` overrides one in `mbed_lib.json`.
 
 The presence of any of these parameters defines `APPLICATION_ADDR` and `APPLICATION_SIZE` for C and C++ and `MBED_APP_START` and `MBED_APP_SIZE` for the linker.
 
@@ -43,8 +43,4 @@ This parameter restricts the size of the application to be at most the specified
 
 The start address of the current application, as computed above, is available to C and C++ as `APPLICATION_ADDR` and to the linker as `MBED_APP_START`. The size of the current application is available as `APPLICATION_SIZE` and `MBED_APP_SIZE`. This parameter also defines `POST_APPLICATION_ADDR` and `POST_APPLICATION_SIZE` as the start address and size of the region after the application.
 
-You may use this parameter in conjunction with `target.bootloader_img` and conflicts with `target.mbed_app_start` and `target.mbed_app_size`. When used with `target.bootloader_img`, that parameter defines the start of the application. Otherwise, the start is the start of ROM.
-
-### Exporter limitations
-
-Although the exporters can export a project using the configuration parameters above, there are some limitations. The exporters do not implement the postbuild merge that managed bootloader builds use. After exporting a project with the `target.bootloader_img` setting, you are responsible for flashing the binary mentioned in the configuration parameter.
+You may use this parameter in conjunction with `target.bootloader_img`. It conflicts with `target.mbed_app_start` and `target.mbed_app_size`. When used with `target.bootloader_img`, that parameter defines the start of the application. Otherwise, the start is the start of ROM.