Merge pull request #912 from grego952/main

Update Kyma tutorials

Author: grego952

tutorials/deploy-to-kyma/deploy-to-kyma.md

@@ -399,11 +399,45 @@ Kyma runs on containers. Hence, for this tutorial, you'll need an application th
 
     Check [Accessing Business Service UI](https://help.sap.com/docs/btp/sap-business-technology-platform/accessing-business-service-ui?locale=39723061bc4b4b679726b120cbefdf5a.html&q=base%20URL) for more information.
 
-5. Create a new folder **ui-resources** in your project's root folder.
+5. Add navigation configuration and deploy configuration to the **app/incidents/webapp/manifest.json** file:
+
+    ```json[9-22,25-28]
+    {
+        "_version": "1.49.0",
+        "sap.app": {
+            "id": "ns.incidents",
+            ...
+            "dataSources": {
+                ...
+            },
+            "crossNavigation": {
+                "inbounds": {
+                    "incidents-display": {
+                        "semanticObject": "incidents",
+                        "action": "display",
+                        "title": "{{flpTitle}}",
+                        "subTitle": "{{flpSubtitle}}",
+                        "signature": {
+                            "parameters": {},
+                            "additionalParameters": "allowed"
+                        }
+                    }
+                }
+            }
+        },
+        ...
+        "sap.cloud": {
+            "public": true,
+            "service": "incidents"
+        }
+    }
+    ```
+
+6. Create a new folder **ui-resources** in your project's root folder.
 
     The HTML5 applications deployer looks for the **ui-resources** folder which has the static files of the HTML5 application.
 
-6. Create a new file **package.json** inside the **ui-resources** folder and add the following code to the file:
+7. Create a new file **package.json** inside the **ui-resources** folder and add the following code to the file:
 
     ```json
     {
@@ -432,21 +466,21 @@ Kyma runs on containers. Hence, for this tutorial, you'll need an application th
 
     ```
 
-7. In the VS Code terminal, navigate to the **ui-resources** folder and run the following command:
+8. In the VS Code terminal, navigate to the **ui-resources** folder and run the following command:
 
     ```bash
     npm install && npm run package
     ```
 
     This will build and copy the archive **nsincidents.zip** inside the **ui-resources/resources** folder.
 
-8. In the VS Code terminal, navigate back to the root folder of your project:
+9.  In the VS Code terminal, navigate back to the root folder of your project:
 
     ```bash
     cd ..
     ```
 
-9. Build the UI deployer image:
+10. Build the UI deployer image:
 
     ```bash
     pack build <your-container-registry>/incident-management-html5-deployer:<image-version> \

tutorials/prepare-btp-kyma/hana-save-mapping.png

@@ -221,7 +221,7 @@ You need the SAP BTP Operator module to map your SAP HANA Cloud service instance
 
 5. Under **Environment Instance ID**, paste the GUID of your Kyma cluster. Here's how to find it:
 
-      - Open you Kyma Console.
+      - Open your Kyma dashboard.
       - Choose **Namespaces** on the left and choose **kyma-system**. 
       - Navigate to **Configuration** → **Config Maps** and choose **sap-btp-operator-config**.
       - You can see the GUID of your Kyma cluster in the **CLUSTER_ID** section.
@@ -230,7 +230,7 @@ You need the SAP BTP Operator module to map your SAP HANA Cloud service instance
     
     > If no namespace is provided, the instance is mapped to all namespaces in the cluster.
 
-5. Choose **Review and Save** and then choose **Save Changes with Restart** in the popup. 
+6. Choose **Review and Save**. In the popup, mark **Apply changes with a restart**, and choose **Save Changes**. 
 
       <!-- border; size:540px --> ![Save changes](./hana-save-mapping.png)
 

tutorials/prepare-btp-kyma/prepare-btp-kyma.md

@@ -103,7 +103,7 @@ In this example, we'll be creating a repository on GitHub. You'll need a [GitHub
 
     <!-- border; size:540px --> ![Continuous Integration and Delivery create service](./cicd-create-service.png)
 
-3. Choose **Create** in the **New Instance or Subscription** popup, and select **default** from the **Plan** field.
+3. In the **New Instance or Subscription** popup select **default** from the **Plan** field.
 
 4. Choose **View Subscription** and wait until the status changes to **Subscribed**.
 
@@ -138,15 +138,15 @@ In this example, we'll be creating a repository on GitHub. You'll need a [GitHub
 
 In order to run the pipeline using the SAP Continuous Integration and Delivery service, you need to create a service account. This is a non-human account that provides a distinct identity in your Kyma cluster. The service account will authenticate your CI/CD pipeline to access your Kyma cluster. See [Service Accounts](https://kubernetes.io/docs/concepts/security/service-accounts/).
 
-1. Navigate to your subaccount and choose **Link to dashboard** under the **Kyma Environment** tab to open the Kyma Console.
+1. Navigate to your subaccount and choose **Link to dashboard** under the **Kyma Environment** tab to open Kyma dashboard.
 
       <!-- border; size:540px --> ![Open Kyma console](./kyma-console.png)
 
 2. Choose **Namespaces** &rarr; **Create**.
 
     <!-- border; size:540px --> ![Create namespace](./create-namespace.png)
 
-3. Enter a name for your namespace (for example, **incident-management-namespace**), switch the **Side Car Injection** toggle **ON**, and choose **Create**.
+3. Enter a name for your namespace (for example, **incident-management-namespace**), switch the **Enable Sidecar Injection** toggle **ON**, and choose **Create**.
 
     <!-- border; size:540px --> ![Create namespace dialog](./create-namespace-dialog.png)