Merge pull request #24198 from sap-tutorials/fix/md-source-1963-batch-6

Fix malformed markdown at source (#1963) (batch 6/15)

Author: jung-thomas

tutorials/cp-cf-events-overview/cp-cf-events-overview.md

@@ -35,7 +35,7 @@ cf events cf-nodejs
 
 You will be greeted by output showing the last 50 events that have occurred in relation to the application.
 
-<!-- border -->![cf events example](cf-events.png)
+![cf events example](cf-events.png)
 
 
 ### Events through the CF API

tutorials/cp-cf-forward-logs-metrics/cp-cf-forward-logs-metrics.md

@@ -59,7 +59,7 @@ $ cf create-user-provided-service <drain-name> -l <drain-url>
   - `drain-name`: any name you would like to use for your drain service
   - `drain-url`: the URL provided by the third-party service for long-term persistence (storage)
 
-<!-- border -->![Create a drain service](create-drain.png)
+![Create a drain service](create-drain.png)
 
 Next, bind an app to the service by specifying the service in the manifest, or running:
 
@@ -70,7 +70,7 @@ $ cf bind-service <app-name> <drain-name>
   - `app-name`: the name of the app you want to get logs _from_
   - `drain-name`: the name of the service you created in step 1 above
 
-<!-- border -->![Bind the service](bind-service.png)
+![Bind the service](bind-service.png)
 
 Finally, you need to restage your application so it picks up the configuration changes. Simply restarting the application does not pick up the changes.
 

tutorials/cp-cf-overview-application-metrics/cp-cf-overview-application-metrics.md

@@ -90,7 +90,7 @@ Now that you know about the CPU, disk, and memory metrics, you probably also wan
 cf app cf-nodejs
 ```
 
-<!-- border -->![Using the cf apps command](cf-app-cf-nodejs.png)
+![Using the cf apps command](cf-app-cf-nodejs.png)
 
 
 ### View metrics with the log cache plugin
@@ -102,7 +102,7 @@ The log cache, besides storing logs, also stores container metrics. Viewing metr
 cf tail -c metrics cf-nodejs
 ```
 
-<!-- border -->![Viewing metrics with log cache](cf-log-cache-metrics.png)
+![Viewing metrics with log cache](cf-log-cache-metrics.png)
 
 
 ---

tutorials/cp-cf-understand-application-lifecycle/cp-cf-understand-application-lifecycle.md

@@ -48,19 +48,19 @@ Once you run the command you will see lots of output print to the screen, and if
 
 The uploading phase begins as follows:
 
-<!-- border -->![Uploading](uploading-phase.png)
+![Uploading](uploading-phase.png)
 
 After that, the staging phase begins. You can see the buildpacks being downloaded (since a specific buildpack is not specified it downloads all of them):
 
-<!-- border -->![Staging Begins](staging-phase.png)
+![Staging Begins](staging-phase.png)
 
 You can also see when the droplet get uploaded:
 
-<!-- border -->![Droplet uploaded](droplet-uploaded.png)
+![Droplet uploaded](droplet-uploaded.png)
 
 And finally you see the starting phase:
 
-<!-- border -->![Application starting](starting-phase.png)
+![Application starting](starting-phase.png)
 
 > If you run `cf push` for an existing application, _all instances of that application are stopped_ and new instances are started with the code you just pushed. Users that try to access the app during this time may get various HTTP error messages, such as "404" ("file not found") and others, while the application is redeployed. The Cloud Foundry API `v3` support the so called [Rolling App Deployments](https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html) with `cf push <app-name> --strategy rolling` which allows to push an app without downtime. The API `v3` are also supported on SAP BTP.
 

tutorials/cp-cf-understand-docker-application-lifecycle/cp-cf-understand-docker-application-lifecycle.md

@@ -67,7 +67,7 @@ docker build -t <username>/cf-nodejs-app .
 
 You should see output similar to the following:
 
-<!-- border -->![Running docker build](docker-build.png)
+![Running docker build](docker-build.png)
 
 Now that the image is built, you need to push it to a repository on `Dockerhub`. Running the following commands, a repository will be created for your user called `cf-nodejs-app` and your image will be uploaded to it:
 
@@ -76,7 +76,7 @@ docker login -u <docker-id>
 docker push <username>/cf-nodejs-app
 ```
 
-<!-- border -->![Pushing the Docker image](docker-push.png)
+![Pushing the Docker image](docker-push.png)
 
 Finally, once the image has been uploaded, you can push the image to Cloud Foundry (you can replace the name `docker-nodejs` with whatever you want to name your application).
 
@@ -94,7 +94,7 @@ cf app docker-nodejs
 
 You should then see the `docker image` field with the name your Docker image next to it, similar to the output below.
 
-<!-- border -->![Link text e.g., Destination screen](docker-image.png)
+![Link text e.g., Destination screen](docker-image.png)
 
 After running through this example, you can see that using a Docker image requires you to specify and configure things that you didn't have to be concerned with when using a buildpack. A buildpack handles most of this in the background for you.
 

tutorials/cp-cf-workflowmanagement-configuremd/cp-cf-workflowmanagement-configuremd.md

@@ -33,13 +33,13 @@ You configure the auto approval policy using this tutorial. This policy is used
 
 1. Choose the **Process Flexibility Cockpit**. Then navigate to **My Live Processes** section and choose **Sample Capital Expenditure Approval Process** tile.
 
-    <!-- border -->![PFC](cp-cf-wm-configuredecision-home2.png)
+    ![PFC](cp-cf-wm-configuredecision-home2.png)
 
-    <!-- border -->![Capital Expenditure](cp-cf-wm-discover-importedcapex0.png)
+    ![Capital Expenditure](cp-cf-wm-discover-importedcapex0.png)
 
 2. Choose the **Determine All Approvers** decision.
 
-    <!-- border -->![Manage decisions](cp-cf-wm-configuredecision-determine.png)
+    ![Manage decisions](cp-cf-wm-configuredecision-determine.png)
 
     You are now in the **Manage Decisions** view.
 
@@ -49,42 +49,42 @@ You configure the auto approval policy using this tutorial. This policy is used
 
 1. Choose the **Determine All Approvers** decision, then choose **Copy to Draft** to create a draft version of the decision.
 
-    <!-- border -->![Copy to Draft](cp-cf-wm-configuredecision-copy.png)
+    ![Copy to Draft](cp-cf-wm-configuredecision-copy.png)
 
 2. In the warning dialog, choose **Continue**.
 
     ![Copy Confirm](cp-cf-wm-configuredecision-warning.png)
 
 3.  Choose the draft version of the decision, and then choose **Policies** > **Auto Approval Policy**.
 
-    <!-- border -->![Auto app](cp-cf-wm-configuredecision-autoapp.png)
+    ![Auto app](cp-cf-wm-configuredecision-autoapp.png)
 
 4. Choose the **Auto Approval** rule.
 
-    <!-- border -->![Auto App Rule](cp-cf-wm-configuredecision-autorule.png)
+    ![Auto App Rule](cp-cf-wm-configuredecision-autorule.png)
 
 5. Choose **Edit**.
 
-    <!-- border -->![Edit Rule](cp-cf-wm-configuredecision-edit.png)
+    ![Edit Rule](cp-cf-wm-configuredecision-edit.png)
 
 6. Modify the text rule value to **`5000`** and **Save** the changes.
 
-    <!-- border -->![Text Rule Value](cp-cf-wm-configuredecision-autovalue.png)
+    ![Text Rule Value](cp-cf-wm-configuredecision-autovalue.png)
 
 
 ### Release and activate decision
 
 1. Choose **Release Version**.
 
-    <!-- border -->![Release Version](cp-cf-wm-configuredecision-release.png)
+    ![Release Version](cp-cf-wm-configuredecision-release.png)
 
 2. In the **Release Version** dialog, provide the revision number and description. Then choose **Release**.
 
-    <!-- border -->![Release](cp-cf-wm-configuredecision-releasedialog.png)
+    ![Release](cp-cf-wm-configuredecision-releasedialog.png)
 
 3. Choose the decision with the version number from the previous step and then choose **Activate**.
 
-    <!-- border -->![Activate Decision](cp-cf-wm-configuredecision-activate.png)
+    ![Activate Decision](cp-cf-wm-configuredecision-activate.png)
 
     You have now modified the decision for your package.
 

tutorials/cp-cf-workflowmanagement-configurepv/cp-cf-workflowmanagement-configurepv.md

@@ -31,28 +31,28 @@ In this tutorial, you can configure one such approval step and activate a proces
 
 1. In the **Process Flexibility Cockpit**, navigate to **My Live Processes** section and choose **Sample Capital Expenditure Approval Process** tile.
 
-    <!-- border -->![CAPEX](cp-cf-wm-discover-importedcapex0.png)
+    ![CAPEX](cp-cf-wm-discover-importedcapex0.png)
 
 2. Choose the **Process Variants** tile.
 
-    <!-- border -->![Variants](cp-cf-wm-configurepv-variantstile.png)
+    ![Variants](cp-cf-wm-configurepv-variantstile.png)
 
 
 ### Create a new variant
 
 1. Choose **New Process Variant**.
 
-    <!-- border -->![New Variant](cp-cf-wm-configurepv-variantnew.png)
+    ![New Variant](cp-cf-wm-configurepv-variantnew.png)
 
 2. Provide **High Value Investments** as the **Name**. Then choose **Create**.
 
-    <!-- border -->![High Value Variant](cp-cf-wm-configurepv-variantname.png)
+    ![High Value Variant](cp-cf-wm-configurepv-variantname.png)
 
     > The **Process** dropdown is preselected as **`Sample Capital Expenditure Approval Process`**. This process refers to the template from which the new variant will be created. A template contains the process steps that are used to configure the different process variants based on business needs.
 
 3. The new process variant is now created with the given name and default description. Choose the newly created **High Value Investments** process variant tile.
 
-    <!-- border -->![High Value Tile](cp-cf-wm-configurepv-highval.png)
+    ![High Value Tile](cp-cf-wm-configurepv-highval.png)
 
     You are now in the **Manage Process Variants** view.
 
@@ -62,19 +62,19 @@ In this tutorial, you can configure one such approval step and activate a proces
 
 1. In the **Manage Process Variants** view, add a new approval step to the template by dragging the **Approval** tile from **Available Steps** and drop it after the **Local Manager Approval** step.
 
-    <!-- border -->![Variant Editor](cp-cf-wm-configurepv-approvaldrag.png)
+    ![Variant Editor](cp-cf-wm-configurepv-approvaldrag.png)
 
     >Choose the new approval step that opens the **Step Properties**
 
-    ><!-- border -->![Variant Editor two](cp-cf-wm-configurepv-newapprovalpng.png)
+    >![Variant Editor two](cp-cf-wm-configurepv-newapprovalpng.png)
 
 2. In the **Step Properties** section, modify the name of the step to **`CFO Approval`**.
 
-    <!-- border -->![Variant Editor two](cp-cf-wm-configurepv-properties1.png)
+    ![Variant Editor two](cp-cf-wm-configurepv-properties1.png)
 
 3. Choose the **Details** tab, then change the **Role Name** to **`CFO`** and **Approval Step** to **`CFO`**.
 
-    <!-- border -->![Group Head Details](cp-cf-wm-configurepv-details.png)
+    ![Group Head Details](cp-cf-wm-configurepv-details.png)
 
     >In the **Details** section, you should provide information on the role of the persona that should perform the approval task.
 
@@ -84,7 +84,7 @@ In this tutorial, you can configure one such approval step and activate a proces
 
 5. Navigate to the Workflow Management home screen.
 
-    <!-- border -->![Home screen](cp-cf-wm-configuredecision-home.png)
+    ![Home screen](cp-cf-wm-configuredecision-home.png)
 
 
 ---

tutorials/cp-cf-workflowmanagement-discover/cp-cf-workflowmanagement-discover.md

@@ -34,17 +34,17 @@ In this tutorial, you can import a sample package with different artifacts using
 
 1. From your global account page, choose the **trial** tile to access your subaccount.
 
-    <!-- border -->![Trial](cp-cf-wm-discover-trial.png)
+    ![Trial](cp-cf-wm-discover-trial.png)
 
 2. Click **Connectivity | Destinations** from the left-hand navigation.
 
-    <!-- border -->![Destination screen](cp-cf-wm-discover-trialdestination.png)
+    ![Destination screen](cp-cf-wm-discover-trialdestination.png)
 
 3. Search for the `WM_CF_SPACE_PROVIDER` destination, then choose the edit icon. In the **Destination Configuration** section, enter your SAP BTP trial user password and save the changes.
 
-    <!-- border -->![Edit Destination](cp-cf-wm-discover-editdestination.png)
+    ![Edit Destination](cp-cf-wm-discover-editdestination.png)
 
-    <!-- border -->![Destination Password](cp-cf-wm-discover-destinationpassword.png)
+    ![Destination Password](cp-cf-wm-discover-destinationpassword.png)
 
     Ensure to replace the dummy password that is provided upon running the booster.
     > Ensure that the credentials of the trial user that are entered in the destination do not have **Two Factor Authentication enabled**.
@@ -53,15 +53,15 @@ In this tutorial, you can import a sample package with different artifacts using
 
 1. Navigate to **Services | Service Marketplace**.
 
-    <!-- border -->![Subscriptions](cp-cf-wm-discover-subscription.png)
+    ![Subscriptions](cp-cf-wm-discover-subscription.png)
 
 2. Search for the **Workflow Management** tile, and choose **Go To Application** to access the workflow management home screen.
 
-    <!-- border -->![Workflow App](cp-cf-wm-discover-goto.png)
+    ![Workflow App](cp-cf-wm-discover-goto.png)
 
 3. In the **Workflow Management** home screen, choose **Process Flexibility Cockpit** tile.
 
-    <!-- border -->![Workflow Management](cp-cf-wm-discover-home.png)
+    ![Workflow Management](cp-cf-wm-discover-home.png)
 
 
 ### Discover the capital expenditure package
@@ -73,7 +73,7 @@ In this tutorial, you can import a sample package with different artifacts using
 
 2.  Choose the **Sample Capital Expenditure Approval Process** tile.
 
-    <!-- border -->![Process Hub](cp-cf-wm-discover-capex.png)
+    ![Process Hub](cp-cf-wm-discover-capex.png)
 
 
 
@@ -82,20 +82,20 @@ In this tutorial, you can import a sample package with different artifacts using
 
 1. Choose **Import**.
 
-    <!-- border -->![Import](cp-cf-wm-discover-import.png)
+    ![Import](cp-cf-wm-discover-import.png)
 
 2. In the confirmation dialog, choose **Import**.
 
-    <!-- border -->![import dialog](cp-cf-wm-discover-importconfirm.png)
+    ![import dialog](cp-cf-wm-discover-importconfirm.png)
 
     > The import operation takes a few minutes for the package to import. If the package import fails for any reason, then you can check the **Import Logs** to identify the cause. Fix the cause and try to import again.
 
 3. Navigate to the **My Live Processes** section.
 
-    <!-- border -->![Breadcrumb](cp-cf-wm-discover-Breadcrumb.png)
+    ![Breadcrumb](cp-cf-wm-discover-Breadcrumb.png)
 
     > You can view the imported **Sample Capital Expenditure Approval Process** package.
 
-    ><!-- border -->![Live Processes](cp-cf-wm-discover-importedcapex.png)
+    >![Live Processes](cp-cf-wm-discover-importedcapex.png)
 
 

tutorials/cp-cf-workflowmanagement-explorepvs/cp-cf-workflowmanagement-explorepvs.md

@@ -29,41 +29,41 @@ In this tutorial, you explore the application, modify a performance indicator, a
 
 1. Choose **Home** to navigate to the home screen.
 
-    <!-- border -->![Home screen](cp-cf-wm-home.png)
+    ![Home screen](cp-cf-wm-home.png)
 
     From the home screen navigate to the **Process Flexibility Cockpit**.
 
-    <!-- border -->![PFC](cp-cf-wm-pfc.png)
+    ![PFC](cp-cf-wm-pfc.png)
 
 2. In the **Process Flexibility Cockpit**, navigate to **My Live Processes** section and choose the **Sample Capital Expenditure Approval Process** tile.
 
-    <!-- border -->![CAPEX](cp-cf-wm-discover-importedcapex.png)
+    ![CAPEX](cp-cf-wm-discover-importedcapex.png)
 
 3. From the **Visibility Scenarios** tile, choose **Sample Capital Expenditure Approval Dashboard**.
 
-    <!-- border -->![Visibility Scenarios](cp-cf-wm-pvcapex.png)
+    ![Visibility Scenarios](cp-cf-wm-pvcapex.png)
 
     You are now in the **Configure Visibility Scenarios** view.
 
-    <!-- border -->![Configure Visibility Scenarios](cp-cf-wm-configscenariosview.png)
+    ![Configure Visibility Scenarios](cp-cf-wm-configscenariosview.png)
 
 
 ### Modify performance indicators
 
 1. Choose the **Performance Indicators** tab.
 
-    <!-- border -->![Performance Indicators](cp-cf-wm-ppi.png)
+    ![Performance Indicators](cp-cf-wm-ppi.png)
 
 2. Choose **Approved Capital Expenditure Requests** and change the **Representation** to **Bar Chart**. Once done, choose **Save**.
 
-    <!-- border -->![Edit Performance Indicators](cp-cf-wm-ppiedit.png)
+    ![Edit Performance Indicators](cp-cf-wm-ppiedit.png)
 
 
 ### Activate the visibility scenario
 
 Choose **Activate**.
 
-<!-- border -->![Activate Visibility Scenario](cp-cf-wm-explorepv-activate.png)
+![Activate Visibility Scenario](cp-cf-wm-explorepv-activate.png)
 
 The successful activation message appears.