Fix MTA Deploy Exercise

Author: jung-thomas

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+    "SAP HANA Database Explorer.displaySapWebAnalyticsStartupNotification": false,
+    "SAP HANA Database Artifacts.displaySapWebAnalyticsStartupNotification": false
+}

tutorials/hana-cloud-cap-deploy-mta/hana-cloud-cap-deploy-mta.md

@@ -52,17 +52,17 @@ Note:  This is an optional tutorial as part of this mission on SAP HANA Cloud pl
 
 6. The rest of the adjustments we need to make are all in the `mta.yaml` file in the root of the project. This is the file that will control the build and deployment of the application.
 
-7. The first adjustment we want to make is to the database module section. We added `default-env.json` and `.env` files to the project so that we could deploy and test from the SAP Business Application Studio.  However we don't want these files to be present in a "real" deployment, instead getting configuration from the bound service instances. Therefore we can tell the builder to exclude these files from this module as well as any other build content (such as the `node_modules` folder). That way we can keep these files in our project for future testing and development but ensure that they don't accidentally make it into a production deployment.
+7. The first adjustment we want to make is to the database module section. We added `default-env.json` and `.env` files to the project so that we could deploy and test from the SAP Business Application Studio.  However we don't want these files to be present in a "real" deployment, instead getting configuration from the bound service instances. Therefore we can tell the builder to exclude these files from this module. That way we can keep these files in our project for future testing and development but ensure that they don't accidentally make it into a production deployment.
 
     !![mta.yaml database module build parameters](mta_db_adjustments.png)
 
-9. The next adjustment to `mta.yaml` is rather substantial. There are different ways to deploy the UI content of our project. We could use standalone application router, managed application router, Fiori launchpad, and/or the HTML5 repository. The wizard that we've used previously setup our project to use a standalone application router but also the HTML5 repository. For your project needs you might decide on different combination of these options and you should explore the impact that each choice has on your deployment approach. However for this tutorial, we've chosen to stay with the standalone application router, but not to use the HTML5 repository. This is a choice that simplifies the setup and is good for small scale applications where you don't mind keeping the UI5 content local within the application router service itself. Therefore we can simply remove all the references and dependencies to the HTML5 Repository and UI Deployer in your `mta.yaml` file.
+8. The next adjustment to `mta.yaml` is rather substantial. There are different ways to deploy the UI content of our project. We could use standalone application router, managed application router, Fiori launchpad, and/or the HTML5 repository. The wizard that we've used previously setup our project to use a standalone application router but also the HTML5 repository. For your project needs you might decide on different combination of these options and you should explore the impact that each choice has on your deployment approach. However for this tutorial, we've chosen to stay with the standalone application router, but not to use the HTML5 repository. This is a choice that simplifies the setup and is good for small scale applications where you don't mind keeping the UI5 content local within the application router service itself. Therefore we can simply remove all the references and dependencies to the HTML5 Repository and UI Deployer in your `mta.yaml` file.
 
     !![Remove UI Deployer and HTML5 Repo from mta.yaml services](mta_approuter_adjustments.png)
 
     Note: If you wanted to keep the HTML5 repository, then some additional changes to the build parameters of the UI Deployer and to the xs-app.json of the application router would be necessary.
 
-10. The last adjustment is a continuation of the previous step.  We need to also remove all references to the HTML Repo and UI Deployer from the resources section of the `mta.yaml` file as well.
+9.  The last adjustment is a continuation of the previous step.  We need to also remove all references to the HTML Repo and UI Deployer from the resources section of the `mta.yaml` file as well.
 
     !![Remove UI Deployer and HTML5 Repo from mta.yaml resources](mta_resources_adjustments.png)