Copy edit Storage.md

Copy edit file for active voice, present tense and other grammar.

Author: Amanda Butler

docs/reference/configuration/Storage.md

@@ -7,8 +7,7 @@ This page describes the build-time configurable parameters for storage in Mbed O
 - [Default BlockDevice configuration](#Default-BlockDevice-configuration).
 - [Default FileSystem configuration](#Default-FileSystem-configuration).
 
-The following is the complete list of storage configuration parameters and how to use and override default implementation if needed.
-For more details regarding configuration parameters please refer [the configuration system documentation](configuration.md).
+Below is the complete list of storage configuration parameters, as generated by `mbed compile --config -v`, and how to use and override default implementation. For more details regarding configuration parameters, please refer to [the configuration system documentation](configuration.md).
 
 ### LittleFS configuration
 
@@ -99,20 +98,23 @@ Name: nvstore.max_keys
 ```
 
 ### BlockDevice - default configuration
-Mbed-os configuration allows you to add block devices as components using the targets json file or target overrides in application config file.
 
-When one of the following components is enabled a default block device will be set in the system.
+The Mbed OS configuration allows you to add block devices as components using the `targets.json` file or target overrides in the application configuration file.
 
-    1. SPIF component.
-    2. DATAFLASH component.
-    3. SD component.
+When one of the following components is enabled, a default block device is set in the system:
+
+1. SPIF component.
+1. DATAFLASH component.
+1. SD component.
 
 Components can coexist in the system. A device can have SPIF and SD or any combination of block devices enabled but only one default block device.
 
-The list above is in precedence order and show which block device will be the default one if more than one component will be enabled.
+The list above is in the order of precedence shows which block device is the default one if more than one component is enabled.
+
+#### Configuring components
 
-#### configuring component:
 Adding "components": ["???"] in targets.json:
+
 ```
     "K64F": {
         "supported_form_factors": ["ARDUINO"],
@@ -134,7 +136,9 @@ Adding "components": ["???"] in targets.json:
         }
     },
 ```
+
 Adding "target.components_add": ["???"] in application config file:
+
 ```     
        "MTB_ADV_WISE_1570": {
             "target.components_add": ["SPIF"],
@@ -143,10 +147,11 @@ Adding "target.components_add": ["???"] in application config file:
        }
 ```
 
-Please note that while a default block device exists an application is not enforced to use it and can create its own one.
+Please note that while a default block device exists, an application is not forced to use it and can create its own one.
 
-#### Overriding default block device implementation 
-The get default instance is implemented as [MBED_WEAK](https://github.com/ARMmbed/mbed-os/blob/40058871de290edc758a21ae6d8f2ec1d1b3533d/platform/mbed_toolchain.h#L120) at features/storage/system_storage/SystemStorage.cpp. That means that it can be overridden by implementing the function without MBED_WEAK and change the default block device for a given application.
+#### Overriding default block device implementation
+
+The get default instance is implemented as [MBED_WEAK](https://github.com/ARMmbed/mbed-os/blob/40058871de290edc758a21ae6d8f2ec1d1b3533d/platform/mbed_toolchain.h#L120) at `features/storage/system_storage/SystemStorage.cpp`. That means that can override it by implementing the function without `MBED_WEAK` and change the default block device for a given application.
 
 ```
 #include "HeapBlockDevice.h"
@@ -160,19 +165,19 @@ BlockDevice *BlockDevice::get_default_instance()
 
 ### FileSystem - default configuration
 
-Mbed-os configuration allows you to add block devices as components using the targets json file or target overrides in application config file.
-When a component of SPIF, DATAFLASH or SD are configured then the system will support one default file system.
+The Mbed OS configuration allows you to add block devices as components using the `targets.json` file or target overrides in the application configuration file. When you configure a component of SPIF, DATAFLASH or SD, the system supports one default file system.
 
-Please note that while a default file system exists an application is not enforced to use it and can create its own one.
+Please note that while a default file system exists, an application is not forced to use it and can create its own one.
 
-The default file system will be created based on the default block device due to performance considerations.
-SPIF and DATAFLASH block devices will support Little file system while SD block device will support FAT file system.
+The default file system is created based on the default block device due to performance considerations.
+
+SPIF and DATAFLASH block devices support the Little file system, and the SD block device supports the FAT file system. However, the application can ovveride this behavior.
 
 #### Overriding default block device implementation
 
-The get default instance is implemented as MBED_WEAK at features/storage/system_storage/SystemStorage.cpp. That means that it can be overridden by implementing the function without MBED_WEAK and change the default block device for a given application.
+The get default instance is implemented as `MBED_WEAK` at `features/storage/system_storage/SystemStorage.cpp`. That means you can overridde it by implementing the function without `MBED_WEAK` and change the default block device for a given application.
 
-The following example will override the get default instance of and will always return a FAT file system regardless of the block device type.
+The following example overrides the get default instance of and always returns a FAT file system regardless of the block device type:
 
 ```
 #include "FATFileSystem.h"
@@ -184,4 +189,4 @@ FileSystem *FileSystem::get_default_instance()
     return &default_fs;
 }
 
-```
+```