Renamed MasterDataModel directory to plural: MasterDataModels

Author: Lutz Ashauer

MasterDataModels/GenericFieldsSchema.md

@@ -34,9 +34,9 @@ The GraphQL schema definition language provides a sustainable starting point, to
 
 [JSON schema validation](https://www.highly.co/hl/rwKOijEQwI4JfP)
 
-[JSON cheat sheet](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModel/Assets/SchemaCheatSheetJSON.pdf)
+[JSON cheat sheet](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModels/Assets/SchemaCheatSheetJSON.pdf)
 
-[GraphQL cheat sheet](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModel/Assets/SchemaCheatSheetGraphQL.pdf)
+[GraphQL cheat sheet](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModels/Assets/SchemaCheatSheetGraphQL.pdf)
 
 ## Schema - Customer Data (example)
 ```javascript
@@ -137,6 +137,6 @@ type NonPhysicalGoods {
 # Sources
 [GraphQL live demo](http://graphql.org/swapi-graphql)
 
-[GraphQL specification - Oct 2016](http://facebook.github.io/graphql/October2016/)
+[GraphQL specification - Oct 2016](http://facebook.github.io/graphql/October2016)
 
 [Generic data model](https://en.wikipedia.org/wiki/Generic_data_model)

MasterDataModels/IntegrationProcess.md

@@ -51,7 +51,7 @@ The master data schema only consists of data fields, that need to be transformed
 
 **NOTE:** A ```businessEntityID``` represents the business subject as a person or an organization. On this approach an inheritance (aka. relation or tree) can be defined by concatenated IDs of those entity types, an aggregate is built of. The usage context (aka. bounded context) is defined by the order of ```.typeObjects```. It is important that the ```.concatinationIDs``` consist of **reference keys**, as a logical syntax.
 
-![Generic fields - concatenated typeObjects (trees)](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModel/Assets/GenericFields.svg)
+![Generic fields - concatenated typeObjects (trees)](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModels/Assets/GenericFields.svg)
 
 > What criteria have to be considered for shaping entity types - aggregates derived from bounded context (typical records) as tree structure?
 

MasterDataModels/Roadmap.md

@@ -5,7 +5,7 @@ The master data model will grow with each application (specific data model) that
 
 > The following steps describe a **hands on approach** which results in a master data model - at least the addresses part. Some statements need to be refined due to meetings with domain experts. _Some steps might be skipped in order to result in a master data model._
 
-**NOTE:** The conceptual approach follows the [MasterDataModelAdresses.md](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModel/MasterDataModelAdresses.md). All findings together should foster a robust master data model.
+**NOTE:** The conceptual approach follows the [MasterDataModelAdresses.md](https://github.com/openintegrationhub/Data-and-Domain-Models/blob/master/MasterDataModels/MasterDataModelAdresses.md). All findings together should foster a robust master data model.
 
 ## Identify generic address fields
 * Setup a test case where at least two data models (applications) become synced - **synchronously**