memap doc minor fixes

Author: Marcelo Salazar

docs/memap.md

@@ -2,11 +2,11 @@
 
 ## Introduction
 
-*memap* is a simple utility useful to display static memory information required by [mbed](https://github.com/mbedmicro/mbed) applications. This information is produced by analysing the memory map file previously generated by your toolchain.
+*memap* is a simple utility that displays static memory information required by [mbed](https://github.com/mbedmicro/mbed) applications. This information is produced by analysing the memory map file previously generated by your toolchain.
 
-Note: this tool is showing static RAM usage and the total size of allocated heap and stack space defined at compile time, not the actual heap and stack usage (which may be different depending on your application).
+**Note**: this tool shows static RAM usage and the total size of allocated heap and stack space defined at compile time, not the actual heap and stack usage (which may be different depending on your application).
 
-## Table of Contents
+## Table of contents
 
 1. [Using memap](#using-memap)
 1. [Information on memory sections](#info-mem-sections)
@@ -15,7 +15,7 @@ Note: this tool is showing static RAM usage and the total size of allocated heap
 
 ## Using memap
 
-*memap* is automatically invoked after an mbed build finishes succesfully. But it's also possible to manually run the program with different command line options, for example:
+*memap* is automatically invoked after an mbed build finishes successfully. It's also possible to manually run the program with different command line options, for example:
 
 ```
 $> python memap.py
@@ -39,7 +39,7 @@ optional arguments:
   -v, --version         show program's version number and exit
 ```
 
-Example:
+Result example:
 
 ```
 $> python memap.py GCC_ARM\myprog3.map -t GCC_ARM
@@ -66,28 +66,25 @@ Total Flash memory (text + data + misc): 66014 bytes
 
 ## Information on memory sections
 
-Find here extended description on the multiple memory sections shown in the previous table.
+The table above showed multiple memory sections.
 
-- text: is where the code application and constants are located in Flash
-- data: non-zero initialized variables; allocated in both RAM and Flash memory (variables are initialized in RAM at run time from Flash)
-- bss: uninitialized data allocated in RAM, or variables initialized to zero
-- heap: dynamic allocated memory defined at build time, usually used by malloc, etc, in RAM
-- stack: used to store local data, temporary data when branching to a subroutine and context switch info; it's considered dynamic allocated memory region in RAM defined at build time
+- ``.text``: is where the code application and constants are located in Flash.
+- ``.data``: non-zero initialized variables; allocated in both RAM and Flash memory (variables are copied from Flash to RAM at run time)
+- ``.bss``: uninitialized data allocated in RAM, or variables initialized to zero.
+- ``Heap``: dynamic allocations in the Heap area in RAM (for example, used by ``malloc``). The maximum size value may be defined at build time.
+- ``Stack``: dynamic allocations in the Stack area in RAM (for example, used to store local data, temporary data when branching to a subroutine or context switch information). The maximum size value may be defined at build time.
 
-On the other hand, there are other entries which do not correspond to modules directly and require a bit of clarification:
+There are other entries that require a bit of clarification:
 
-- Fill: this entry represents the bytes in multiple sections (RAM and Flash) that the toolchain has filled with zeros because requires subsequent data or code to be aligment appropriately in memory
-- Misc: it mainly represents helper libraries introduced by the toolchain (e.g. libc) but there might be other modules not part of mbed
+- Fill: represents the bytes in multiple sections (RAM and Flash) that the toolchain has filled with zeros because it requires subsequent data or code to be aligned appropriately in memory.
+- Misc: usually represents helper libraries introduced by the toolchain (like ``libc``), but can also represent modules that are not part of mbed.
 
 ## Current support
 
-*memap* has been tested on Windows 7, Linux and Mac.
+*memap* has been tested on Windows 7, Linux and Mac OS X and works with memory map files are generated by the GCC_ARM, ARM (ARM Compiler 5) and IAR toochains.
 
-Supported map files generated by the following toolchains: GCC_ARM, ARM (ARM Compiler 5) and IAR.
+## Known issues and new features
 
-## Known problems & New features
+This utility is considered 'alpha' quality at the moment. The information generated by this utility may not be fully accurate and may vary from one toolchain to another.
 
-This utility is considered 'Alpha' quality at the moment.
-Please note, the information generated by this utility may not be fully accurate and may vary from one toolchain to another.
-
-If you are seeing problems or would like new features to be added then please raise a ticket on [GitHub](https://github.com/mbedmicro/mbed/issues) and use ```[memap] ``` in the title.
+If you are experiencing problems, or would like additional features, please raise a ticket on [GitHub](https://github.com/mbedmicro/mbed/issues) and use ```[memap] ``` in the title.