fix(typo): found by misspell (#2064)

* fix typos in step yamls

* fix typos in go files

* regenerate step code

* fix typos in md files

* fix typos in groovy files

* fix further typos

documentation/docs/steps/checkChangeInDevelopment.md

@@ -53,7 +53,7 @@ general:
       format: '%b'
 ```
 
-The properties configured in section `'general/changeManagement'` are shared between all change managment related steps.
+The properties configured in section `'general/changeManagement'` are shared between all change management related steps.
 
 The properties can also be configured on a per-step basis:
 
@@ -77,7 +77,7 @@ The parameters can also be provided when the step is invoked:
 ```
 
 ```groovy
-    // explict endpoint provided, we search for changeDocumentId
+    // explicit endpoint provided, we search for changeDocumentId
     // starting at the previous commit (HEAD~1) rather than on
     // 'origin/master' (the default).
     checkChangeInDevelopment(

documentation/docs/steps/checksPublishResults.md

@@ -86,7 +86,7 @@
 
 ### Thresholds
 
-It is possible to define thresholds to fail the build on a certain count of findings. To achive this, just define your thresholds a followed for the specific check tool:
+It is possible to define thresholds to fail the build on a certain count of findings. To achieve this, just define your thresholds a followed for the specific check tool:
 
 ```groovy
 thresholds: [fail: [all: 999, low: 99, normal: 9, high: 0]]

documentation/docs/steps/gctsCloneRepository.md

@@ -5,7 +5,7 @@
 ## Prerequisites
 
 With this step you can clone a remote Git repository to a local repository on an ABAP server. To be able to execute this step, the corresponding local repository has to exist on the local ABAP system.
-Learn more about the SAP Git-enabled Change & Transport Sytem (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
+Learn more about the SAP Git-enabled Change & Transport System (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
 
 ## ${docGenParameters}
 

documentation/docs/steps/gctsCreateRepository.md

@@ -5,7 +5,7 @@
 ## Prerequisites
 
 With this step you can create a local git-enabled CTS (gCTS) repository on an ABAP server.
-Learn more about the SAP Git-enabled Change & Transport Sytem (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
+Learn more about the SAP Git-enabled Change & Transport System (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
 
 ## ${docGenParameters}
 

documentation/docs/steps/gctsDeploy.md

@@ -5,7 +5,7 @@
 ## Prerequisites
 
 With this step you can deploy a commit from a remote Git repository to a local repository on an ABAP server. If no `commit` parameter is specified, this step will pull the latest commit available on the remote repository.
-Learn more about the SAP Git-enabled Change & Transport Sytem (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
+Learn more about the SAP Git-enabled Change & Transport System (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
 
 ## ${docGenParameters}
 

documentation/docs/steps/gctsExecuteABAPUnitTests.md

@@ -6,7 +6,7 @@
 
 * You have gCTS installed and configured on your ABAP systems.
 
-Learn more about the SAP Git-enabled Change & Transport Sytem (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
+Learn more about the SAP Git-enabled Change & Transport System (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
 
 ## ${docGenParameters}
 

documentation/docs/steps/gctsRollback.md

@@ -5,7 +5,7 @@
 ## Prerequisites
 
 This step performs a rollback of commit(s) in a local ABAP system repository. If a `commit` parameter is specified, it will be used as the target commit for the rollback. If no `commit` parameter is specified and the remote repository domain is 'github.com', the last commit with status 'success' will be used for the rollback. Otherwise, gctsRollback will rollback to the previously active commit in the local repository.
-Learn more about the SAP git-enabled Central Transport Sytem (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
+Learn more about the SAP git-enabled Central Transport System (gCTS) [here](https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/201909.001/en-US/f319b168e87e42149e25e13c08d002b9.html). With gCTS, ABAP developments on ABAP servers can be maintained in Git repositories.
 
 ## ${docGenParameters}
 

documentation/docs/steps/healthExecuteCheck.md

@@ -10,7 +10,7 @@ Endpoint for health check is configured.
     The health endpoint needs to be available without authentication!
 
 !!! tip
-    If using Spring Boot framework, ideally the provided `/health` endpoint is used and extended by development. Further information can be found in the [Spring Boot documenation for Endpoints](http://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-endpoints.html)
+    If using Spring Boot framework, ideally the provided `/health` endpoint is used and extended by development. Further information can be found in the [Spring Boot documentation for Endpoints](http://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-endpoints.html)
 
 ## ${docGenParameters}
 

documentation/docs/steps/influxWriteData.md

@@ -95,7 +95,7 @@ As a first step you need to add your InfluxDB as Data source to your Grafana:
 !!! note "Jenkins as a Service"
     For Jenkins as a Service the data source configuration is already available.
 
-    Therefore no need to go through the data source configuration step unless you want to add addtional data sources.
+    Therefore no need to go through the data source configuration step unless you want to add additional data sources.
 
 ## Data collected in InfluxDB
 

documentation/docs/steps/mavenExecute.md

@@ -17,7 +17,7 @@
     ```
 
     Additionally please note that in the parameters _must not_ be [shell quoted/escaped](https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_03_03.html).
-    What you pass in is literally passed to Maven without any shell interpreter inbetween.
+    What you pass in is literally passed to Maven without any shell interpreter in between.
 
     The old behavior is still available in version `v1.23.0` and before of project "Piper".
 

documentation/docs/steps/transportRequestCreate.md

@@ -46,7 +46,7 @@ general:
 ```
 
 The properties configured in section `'general/changeManagement'` are shared between
-all change managment related steps.
+all change management related steps.
 
 The properties can also be configured on a per-step basis:
 

documentation/docs/steps/transportRequestRelease.md

@@ -45,7 +45,7 @@ general:
       format: '%b'
 ```
 
-The properties configured in section `'general/changeManagement'` are shared between all change managment related steps.
+The properties configured in section `'general/changeManagement'` are shared between all change management related steps.
 
 The properties can also be configured on a per-step basis:
 

documentation/docs/steps/transportRequestUploadFile.md

@@ -47,7 +47,7 @@ general:
       format: '%b'
 ```
 
-The properties configured in section `'general/changeManagement'` are shared between all change managment related steps.
+The properties configured in section `'general/changeManagement'` are shared between all change management related steps.
 
 The properties can also be configured on a per-step basis: