From d2285f892914069ffc987d193b05949f2dc6b08a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tilo=20K=C3=B6rner?=
 <70266685+tiloKo@users.noreply.github.com>
Date: Mon, 22 Jul 2024 14:32:26 +0200
Subject: [PATCH] Update abapAddonAssemblyKitCheck.yaml (#4992)

* Update abapAddonAssemblyKitCheck.yaml

remove bullet points as they are not rendered together with markdown

* Update abapAddonAssemblyKitCheck.yaml

* delete trailing space

* go generate
---
 cmd/abapAddonAssemblyKitCheck_generated.go        | 8 +++-----
 resources/metadata/abapAddonAssemblyKitCheck.yaml | 8 +++-----
 2 files changed, 6 insertions(+), 10 deletions(-)

diff --git a/cmd/abapAddonAssemblyKitCheck_generated.go b/cmd/abapAddonAssemblyKitCheck_generated.go
index 73090511f1..71d2226046 100644
--- a/cmd/abapAddonAssemblyKitCheck_generated.go
+++ b/cmd/abapAddonAssemblyKitCheck_generated.go
@@ -70,11 +70,9 @@ func AbapAddonAssemblyKitCheckCommand() *cobra.Command {
 	var createAbapAddonAssemblyKitCheckCmd = &cobra.Command{
 		Use:   STEP_NAME,
 		Short: "This step calls AAKaaS to check the validity of the Addon Product Modelling.",
-		Long: `This step does the following:<ul>
-  [The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml)
-  A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules)
-  The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps
-</ul>
+		Long: `[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml).
+A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules).
+The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage in subsequent pipeline steps.
 <br />
 For logon to AAKaaS you can either provide a credential with basic authorization (username and password) or two secret text credentials containing the technical s-users certificate (see note [2805811](https://me.sap.com/notes/2805811) for download) as base64 encoded string and the password to decrypt the file
 <br />
diff --git a/resources/metadata/abapAddonAssemblyKitCheck.yaml b/resources/metadata/abapAddonAssemblyKitCheck.yaml
index a7c9859bd5..a5f9463d99 100644
--- a/resources/metadata/abapAddonAssemblyKitCheck.yaml
+++ b/resources/metadata/abapAddonAssemblyKitCheck.yaml
@@ -2,11 +2,9 @@ metadata:
   name: abapAddonAssemblyKitCheck
   description: This step calls AAKaaS to check the validity of the Addon Product Modelling.
   longDescription: |
-    This step does the following:<ul>
-      [The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml)
-      A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules)
-      The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps
-    </ul>
+    [The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml).
+    A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules).
+    The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage in subsequent pipeline steps.
     <br />
     For logon to AAKaaS you can either provide a credential with basic authorization (username and password) or two secret text credentials containing the technical s-users certificate (see note [2805811](https://me.sap.com/notes/2805811) for download) as base64 encoded string and the password to decrypt the file
     <br />