[INTERNAL] UA Review README.md

Author: SabineLoss

README.md

@@ -1,7 +1,7 @@
 ![UI5 icon](https://raw.githubusercontent.com/SAP/ui5-tooling/master/docs/images/UI5_logo_wide.png)
 
 # ui5-project
-> Modules for building a UI5 projects dependency tree, including configuration  
+> Modules for building a UI5 projects dependency tree, including configuration.  
 > Part of the [UI5 Build and Development Tooling](https://github.com/SAP/ui5-tooling)
 
 [![Travis CI Build Status](https://travis-ci.org/SAP/ui5-project.svg?branch=master)](https://travis-ci.org/SAP/ui5-project)
@@ -16,15 +16,15 @@
 ## Normalizer
 The purpose of the normalizer is to collect dependency information and to enrich it with project configuration ([generateProjectTree](https://github.com/pages/SAP/ui5-tooling/module-normalizer_normalizer.html#~generateProjectTree)).
 
-[Translators](#translators) are used to collect dependency information. The [Project Preprocessor](#project-preprocessor) enriches this dependency information with project configuration. Typically from a `ui5.yaml` file. A development server and build process can use this information to locate project- and dependency resources.
+[Translators](#translators) are used to collect dependency information. The [Project Preprocessor](#project-preprocessor) enriches this dependency information with project configuration, typically from a `ui5.yaml` file. A development server and build process can use this information to locate project and dependency resources.
 
-To only retrieve the project dependency graph, please use ([generateDependencyTree](https://github.com/pages/SAP/ui5-tooling/module-normalizer_normalizer.html#~generateDependencyTree)).
+If you want to retrieve the project dependency graph only, use ([generateDependencyTree](https://github.com/pages/SAP/ui5-tooling/module-normalizer_normalizer.html#~generateDependencyTree)).
 
 ## Translators
-Translators collect recursively all dependencies on a package manager specific layer and return information about them in a well-defined tree-structure.
+Translators collect recursively all dependencies on a package manager specific layer and return information about them in a well-defined tree structure.
 
-### Tree structure returned by a translator
-The following dependency tree is the expected input structure of the [Project Preprocessor](#project-preprocessor).
+### Tree Structure Returned by a Translator
+The following dependency tree is the expected input structure of the [Project Preprocessor](#project-preprocessor):
 
 ````json
 {
@@ -58,14 +58,14 @@ The following dependency tree is the expected input structure of the [Project Pr
 ````
 
 ### npm Translator
-The npm translator is currently the default translator and looks for dependencies defined in the `package.json` file of a certain project. `dependencies`, `devDepedencies` and [napa dependencies](https://github.com/shama/napa) (Git repositories which don't have a `package.json` file) are located via the Node.js module resolution logic.
+The npm translator is currently the default translator and looks for dependencies defined in the `package.json` file of a certain project. `dependencies`, `devDepedencies`, and [napa dependencies](https://github.com/shama/napa) (Git repositories which don't have a `package.json` file) are located via the Node.js module resolution logic.
 
 ### Static Translator
 *This translator is currently intended for testing purposes only.*
 
 Can be used to supply the full dependency information of a project in a single structured file.
 
-Usage example: `ui5 serve -b static:/path/to/projectDependencies.yaml`  
+Example: `ui5 serve -b static:/path/to/projectDependencies.yaml`  
 `projectDependencies.yaml` contains something like:
 ````yaml
 ---
@@ -85,7 +85,7 @@ dependencies:
 ## Project Preprocessor
 Enhances a given dependency tree based on a projects [configuration](#configuration).
 
-### Enhanced dependency tree structure returned by the Project Preprocessor
+### Enhanced Dependency Tree Structure Returned by the Project Preprocessor
 ````json
 {
     "id": "projectA",
@@ -183,8 +183,8 @@ Enhances a given dependency tree based on a projects [configuration](#configurat
 ````
 
 ## Configuration
-### Project configuration
-Typically located in a per-project `ui5.yaml` file.
+### Project Configuration
+Typically located in a `ui5.yaml` file per project.
 
 #### Structure
 ##### YAML
@@ -230,10 +230,10 @@ server:
 #### Properties
 ##### \<root\>
 - `specVersion`: Version of the specification
-- `type`: Either `application`, `library` or `custom` (custom not yet implemented). Defines default path mappings and build steps. Custom doesn't define any specific defaults
+- `type`: Either `application`, `library` or `custom` (custom not yet implemented); defines the default path mappings and build steps. Custom doesn't define any specific defaults.
 
 ##### metadata
-Some general information
+Some general information:
 - `name`: Name of the application/library/resource
 - `copyright` (optional): String to be used for replacement of copyright placeholders in the project
 
@@ -242,17 +242,17 @@ Some general information
     - `paths`: Mapping between virtual and physical paths
         + For type `application` there can be a setting for mapping the virtual path `webapp` to a physical path within the project
         + For type `library` there can be a setting for mapping the virtual paths `src` and `test` to physical paths within the project
-- `shims`: Can be used to define, extend or override UI5 configs of dependencies. Inner structure equals the general structure. It is a key-value map where the key equals the project ID as supplied by the translator.
+- `shims`: Can be used to define, extend, or override UI5 configs of dependencies. Inner structure equals the general structure. It is a key-value map where the key equals the project ID as supplied by the translator.
 
 ##### builder (optional)
-- `customTasks` (optional, list): in this block you can define additional custom build tasks. Please see [here](docs/BuildExtensibility.md) for a detailed explanation and examples of the build extensibility. Each entry in the `customTasks` list consists of the following options:
-  - `name` (mandatory): the name of the custom task
-  - `afterTask` or `beforeTask` (only one, mandatory): the name of the build task after or before which your custom task will be executed.
-  - `configuration` (optional): additional configuration that will be passed to the custom build task
+- `customTasks` (optional, list): In this block, you define additional custom build tasks, see [here](docs/BuildExtensibility.md) for a detailed explanation and examples of the build extensibility. Each entry in the `customTasks` list consists of the following options:
+  - `name` (mandatory): The name of the custom task
+  - `afterTask` or `beforeTask` (only one, mandatory): The name of the build task after or before which your custom task will be executed.
+  - `configuration` (optional): Additional configuration that is passed to the custom build task
 
 ##### server (optional)
 - `settings` (not yet implemented)
-    - `port`: Project default server port. Can be overwritten via CLI parameters.
+    - `port`: Project default server port; can be overwritten via CLI parameters
 
 ## Contributing
 Please check our [Contribution Guidelines](https://github.com/SAP/ui5-tooling/blob/master/CONTRIBUTING.md).