fix: JO feedback is added

docs/tutorials/2018-04-28-schema-update-tutorial.md

@@ -17,8 +17,6 @@ This tutorial reviews the steps required to update the schema used in automated
 * a schema(s) for your target data
 * a target theme
 
-*IMPORTANT: The target dataset is automatically generated by the online transformation workflow. The target dataset is typically transformed, INSPIRE GML.*
-
 ### **Tutorial data**
 
 The installation of hale»studio and the creation of alignments are beyond the scope of this tutorial. For more information, visit [hale»studio](https://www.wetransform.to/products/halestudio/).
@@ -30,7 +28,7 @@ For this tutorial, we will use:
 
 The transformation project maps German protected sites data to the INSPIRE feature type ProtectedSite, which is found in the INSPIRE Protected Sites 4.0 schema.
 
-### **Updating an Online Transformation Project**
+### **Updating a Transformation Project**
 
 **Step 1: Open an existing transformation project in hale»studio**
 
@@ -40,7 +38,7 @@ If you have hale»studio installed on your computer, you can load the transforma
 
 **Step 2: Update the INSPIRE schema used by the transformation project**
 
-The next step is to update the schema used in the transformation project.
+The next step is to update the schema used in the transformation project, so that it uses the INSPIRE Protected Sites schema version 5.0 instead of 4.0.
 
 In hale»studio navigate to the File menu and select the option to Reload and update schemas. In the dialog that appears, double-click on the schema URL that is displayed and navigate to the INSPIRE presets and select the INSPIRE Protected Sites 5.0 schema.
 <a className="image-news text-center col-xs-12 mt mb"><img src={require("/images/help/en/update_schemas.png").default} alt="" title="Selecting a new schema" className="img-responsive center-block"/>
@@ -50,17 +48,16 @@ Click &laquo;OK&raquo;. The INSPIRE schema used in the transformation project is
 
 **Step 3: Load source data and complete cell entity matching**
 
-In this step, we will load the source data and complete the steps displayed in the cell entity matching dialogs that appear in hale»studio. Cell entity matching dialogs appear when a schema is changed and hale»studio cannot determine how to update the existing mappings due to changed type or property names. In these cases, the end user must provide hale»studio information on how to update the existing mappings, based on the new schema.
+In this step, we will load the source data and complete the steps displayed in the cell entity matching dialogs that appear in hale»studio. Cell entity matching dialogs appear when a schema is changed and hale»studio cannot determine how to update the existing mappings due to changed type names, property names or changed namespaces. In these cases, the end user must provide hale»studio information on how to update the existing mappings, based on the new schema.
 
-It is useful to review the changes that have been made to the schema you are updating to obtain an overview of the elements that need to be updated.
+It is useful to review the changes that have been made to the schema you are updating to obtain an overview of the elements that need to be updated.  The changes are documented as comments in the INSPIRE \*.xsd schema files available [here](https://inspire.ec.europa.eu/schemas/index.html).
 
 First, load the source data in hale»studio. Navigate to the File menu and select Import, next, select Source data...
 
-Once the source data is loaded, a potentially large number of cell entity dialogs will appear successively until all elements have been updated to reflect the new schema. A complete update requires the end user to manually select the element in the element tree that hale»studio is searching for, for each updated reference. In some cases, hale»studio will correctly identify the matching element in the new schema, in other cases, direct user input is required.
-<a className="image-news text-center col-xs-12 mt mb"><img src={require("/images/help/en/cell_entity_could_not_be_resolved.png").default} alt="" title="Cell entity matching" className="img-responsive center-block"/>
+Once the source data is loaded, a potentially large number of cell entity dialogs will appear successively until all elements have been updated to reflect the new schema. A complete update requires the end user to manually select the element in the element tree that hale»studio is searching for, for each updated reference. In some cases, hale»studio will correctly identify the matching element in the new schema (for example if only the namespace changed but the type and property name remain the same), in other cases, direct user input is required. It is possible to skip one or more mappings in the dialog if the handling is not fully clear. Skipping a mapping allows the end user to continue with automatically assigned, or recognised mappings, without having to cancel the entire process. Unhandled mappings can be edited afterwards in the hale»studio UI. <a className="image-news text-center col-xs-12 mt mb"><img src={require("/images/help/en/cell_entity_could_not_be_resolved.png").default} alt="" title="Cell entity matching" className="img-responsive center-block"/>
 </a>
 
-**Step 4: Check validation and save transformtion project**
+**Step 4: Check validation and save transformation project**
 
 Once all cell entity matching has been completed, take a moment to check the validation of the updated transformation project to ensure that all required schema elements have been handled properly. In hale»studio, open the Report List window to view the status of the instance transformation and the instance validation. A green check indicates a valid project. A yellow warning indicates that the project contains mappings with warnings that can be reviewed in the Properties window. Double-click on the instance transformation and the instance validation text in the Report List window to view more information about warnings in the Properties window.
 
@@ -85,14 +82,14 @@ To create a new schema using a schema preset, follow this workflow logged in as
 
    * Select the INSPIRE Protected Sites 5.0 schema preset from the dropdown list of available presets.<img src={require("/images/help/en/schema_5_en.png").default} alt="" title="Creating a new schema from a preset" className="img-responsive img-inline-help"/>
 
-   * Add information. Provide the name, author, type and version of your schema. Ensure that you select INSPIRE as type from the dropdown menu. When you are finished, click &laquo;Continue&raquo;
+   * Add information. Provide the name, author, type and version of your schema. When you are finished, click &laquo;Continue&raquo;
 
    * Confirm creation. In the final step, review your schema. You have the option to create a theme for your schema. For this workflow, you do not need to enable theme creation. When you are finished, click &laquo;Create&raquo; to save the schema.
 
 
 **Step 2: Update the feature types of the target theme**
 
-The next step is to update the Feature Types section of your INSPIRE Protected Sites 4.0 theme to use the feature types from the INSPIRE Protected Sites 5.0 schema.
+The next step is to update the Feature Types section of your INSPIRE Protected Sites theme to use the feature types from the INSPIRE Protected Sites 5.0 schema.
 
 First, navigate to your existing Protected Sites theme on hale»connect. Select the Feature Types section.
 <img src={require("/images/help/en/update_feature_types_en.png").default} alt="" title="Updating feature types" className="img-responsive img-inline-help"/>
@@ -102,4 +99,4 @@ Click the red "x" to delete the existing feature types and click on &laquo;+ Add
 
 **Step 3: Trigger the updated transformation project and republish existing resources**
 
-Once you have updated your transformation project and updated the feature types in your existing target theme, you can re-run the online transformation to update your published resources on hale»connect. 
+Once you have updated your transformation project and updated the feature types in your existing target theme, you can re-run the online transformation to update your published resources on hale»connect.