Align wording, fix typos

Author: RaphaelKomander

Protocols/2018-01-17Workshop.md

@@ -4,12 +4,12 @@
 
 ## Tasks of the Workgroup
 - The workgroup helps to realize the POC 1 - POC 3 from the [roadmapV1](https://github.com/openintegrationhub/Architecture/blob/roadmap/Roadmap/RoadmapV1.md)
-- Analytical approach to improve the master data models
-  - Evaluating the master data models by comparing them to existing standards (EDIFACT, BiPRO, InfoSphere, etc.)
+- Analytical approach to improve the standard data model (configuration)
+  - Evaluating the standard data model by comparing it to existing standards (EDIFACT, BiPRO, InfoSphere, etc.)
   - Deriving mapping rules to map the "OIH standard" against existing Standards
 - Technical implementation is done by the _architecture workgroup_. See [repository architecture workgroup](https://github.com/openintegrationhub/Architecture)
-- Rules and regulations of the data Models
-  - How do the data models evolve? E.g. What is the process to decide on suggested changes (Versioning)?
+- Rules and regulations of the data models
+  - How do the data models evolve? What is the process to decide on suggested changes (Versioning) - for example?
   - How shall new data models be developed
 - Documentation for the implementation of transformer (mapping)  
 - The workgroup helps to achieve the results of milestone 2 by contributing to the "Access to the OIH platform 0.5" and "Document procedure model for integration cloud provider"
@@ -31,7 +31,7 @@ See the current status of the specs under [DataHub.md](https://github.com/openin
 - Decoupling between adapter and transformer
   - Adapter can talk to the transformer and/or to other adapters. Thus semantic transformation via the transformer and individual integrations are enabled
   -  (Adapter holds syntactically transformed data). Not mandatory: ISV doesn't have to upload the data into the raw data storage.
-- **Meta Data Managmemnt API** uploads the information about the metadata (list of objects)
+- **Meta Data Management API** uploads the information about the metadata (list of objects)
 - **Data Management API** uploads the actual data (data records)
 
 Within the scope of this topic the following illustrations was drawn:
@@ -45,13 +45,13 @@ Within the scope of this topic the following illustrations was drawn:
 Distinction between identity management of the open integration hub (minimal functionality to manage identities) and the domain "roles & right / user & roles"
 
 ## Next Steps / Derived Tasks
-- [ ] Elaborate common structure for the documentation of the master data models (JSON-Schema, UML diagrams, textual description) **Raphael + Lutz**
-- [ ] Expand and further describe the superordinated structure for the domain models (see _OIHDataRecord_) **Raphael + Lutz**
-- [ ] Elaborate/expand rules and regulations for the evolution of master data models (How do the data models evolve?, How shall new models be created, how often are new versions created, ...) **Raphael + Lutz**
+- [ ] Elaborate common structure for the documentation of the standard data model (JSON-Schema, UML diagrams, textual description) **Raphael + Lutz**
+- [ ] Expand and further describe the superordinate structure for the domain models (see _OIHDataRecord_) **Raphael + Lutz**
+- [ ] Elaborate/expand rules and regulations for the evolution of standard data models (How do the data models evolve?, How shall new models be created, how often are new versions created, ...) **Raphael + Lutz**
 - [ ] Consider the "Meta-Meta Model" (Definition used by **Renat**) with respect to the capabilities of the JSON Schema (E.g. types like date, currency, etc.)
-- [ ] Compare master data models with existing standards (EDIFACT, BiPRO, InfoSphere, etc.) **Raphael**
+- [ ] Compare the standard data model (configuration) with existing standards (EDIFACT, BiPRO, InfoSphere, etc.) **Raphael**
 - [ ] Document the current status of the POC 1 (The following steps break down the concrete tasks) **Andy + Josef**
-  - [ ] Create API documentation / interface documentation
+  - [ ] Provide an API documentation / interface documentation - **public**
   - [ ] Create JSONata expression (mapping)
   - [ ] Create a mapping table
   - [ ] Document which elastic.io components where used and why