fix spelling and validator (#18376)

TiaXu1122 · web-flow · commit 683836789460 · 2022-04-28T08:21:29.000+02:00
* fix spelling

* fix validator
diff --git a/tutorials/deploy-nodejs-application-kyma/deploy-nodejs-application-kyma.md b/tutorials/deploy-nodejs-application-kyma/deploy-nodejs-application-kyma.md
@@ -51,22 +51,21 @@ In order to run your code on the Kyma Runtime (or on any Kubernetes-based platfo
 
 The command-line tool `pack` supports providing a buildpack and your local source code and creating an OCI image from it. We are working on a process to provide recommended and supported buildpacks. In the meantime, you can use the community-supported [Paketo Buildpacks](https://paketo.io/).
 
-Install command-line tool `pack`: [Install Pack](https://buildpacks.io/docs/tools/pack/)
+**1.** Install command-line tool `pack`: [Install Pack](https://buildpacks.io/docs/tools/pack/)
 
 For example (macOS):
 
-```shell
+```Shell / Bash
 brew install buildpacks/tap/pack
 ```
 
-
 When we speak about repository name, we mean the combination of account and repo name that is usual with Docker Hub: `<docker-hub-account>/<repo-name>`. An example would be `tiaxu/multitenant-kyma-backend`.
 
 As you can only create one private repository in a free Docker hub account, Docker images stored in Docker hub will have different tag names so that they can be stored under one repository. Thus, addressing an image will include the tag name:`<docker-hub-account>/<repo-name>:<tag-name>`. An example would be `tiaxu/multitenant-kyma-backend:v1`.
 
-Under the directory `kyma-multitenant-node`, build the image for the approuter app from source, for example:
+**2.** In the directory `kyma-multitenant-node`, build the image for the approuter app from source, for example:
 
-```shell
+```Shell / Bash
 pack build multitenant-kyma-backend --builder paketobuildpacks/builder:full
 docker tag multitenant-kyma-backend <docker-hub-account>/multitenant-kyma-backend:v1
 ```
@@ -78,15 +77,15 @@ docker tag multitenant-kyma-backend <docker-hub-account>/multitenant-kyma-backen
 
 [ACCORDION-BEGIN [Step 4: ](Push OCI Image to Docker Hub)]
 
-Log in to Docker using this command:
+**1.** Log in to Docker using this command:
 
-```shell
+```Shell / Bash
 docker login -u <docker-id> -p <password>
 ```
 
-Push the local image into the Docker Hub:
+**2.** Push the local image into the Docker Hub:
 
-```shell
+```Shell / Bash
 docker push <docker-hub-account>/multitenant-kyma-backend:v1
 ```
 
@@ -100,11 +99,11 @@ docker push <docker-hub-account>/multitenant-kyma-backend:v1
 
 Then you are ready to deploy it into the Kubernetes cluster with Kyma runtime.
 
-Select the `Link to dashboard` to open the Kyma dashboard.
+**1.** Select the `Link to dashboard` to open the Kyma dashboard.
 
 ![image-20220112154735200](image-20220112154735200.png)
 
-Create a new namespace through the Kyma dashboard or `kubectl` CLI, for example, called `multitenancy-ns`:
+**2.** Create a new namespace through the Kyma dashboard or `kubectl` CLI, for example, called `multitenancy-ns`:
 
 ![image-20220214150615225](image-20220214150615225.png)
 
@@ -116,13 +115,12 @@ Create a new namespace through the Kyma dashboard or `kubectl` CLI, for example,
 
 [ACCORDION-BEGIN [Step 6: ](Deploy Secret for Docker Hub)]
 
-Since the OCI image is stored in your Docker hub, you need to provide the access information to your Kyma cluster that you can pull the images from those repositories:
+Since the OCI image is stored in your Docker hub, you need to provide the access information to your Kyma cluster that you can pull the images from those repositories, replace the placeholder values according to your account:
 
-```shell
+```Shell / Bash
 kubectl -n multitenancy-ns create secret docker-registry registry-secret --docker-server=https://index.docker.io/v1/  --docker-username=<docker-id> --docker-password=<password> --docker-email=<email>
 ```
 
-> Replace the placeholder values according to your account.
 
 Therefore, all deployment files contain an `imagePullSecret` entry, which should be set to `registry-secret`.
 
@@ -140,7 +138,7 @@ imagePullSecrets:
 
 Based on the previous preparation steps, you can define the description file for deployment.
 
-Under the root directory `multitenancy-kyma-tutorial`, create a new YAML file called `k8s-deployment-backend.yaml` with the following content:
+In the root directory `multitenancy-kyma-tutorial`, create a new YAML file called `k8s-deployment-backend.yaml` with the following content:
 
 ```yaml
 
@@ -314,7 +312,7 @@ spec:
 
 Deploy the Node.js application by executing this command under the root directory `multitenancy-kyma-tutorial`:
 
-```shell
+```Shell / Bash
 kubectl -n multitenancy-ns apply -f k8s-deployment-backend.yaml
 ```
 
@@ -327,16 +325,16 @@ kubectl -n multitenancy-ns apply -f k8s-deployment-backend.yaml
 [ACCORDION-BEGIN [Step 9: ](Access Application in Browser)]
 
 
-Find the URL address of your application in the Kyma dashboard:
+**1.** Find the URL address of your application in the Kyma dashboard:
 
 ![image-20220214153901104](1645680425240.jpg)
 
-Access it in the browser, then the application will return the message that you defined before.
+**2.** Access it in the browser, then the application will return the message that you defined before.
 
 
 
 
-[DONE]
+[VALIDATE_1]
 [ACCORDION-END]
 
 [ACCORDION-BEGIN [Step 10: ](Project Repository)]
diff --git a/tutorials/implement-subscription-callback-multitenant/implement-subscription-callback-multitenant.md b/tutorials/implement-subscription-callback-multitenant/implement-subscription-callback-multitenant.md
@@ -13,7 +13,7 @@ primary_tag: software-product>sap-btp\, kyma-runtime
 ## Details
 ### You will learn
 - How to implement the Subscribe/Unsubscribe callbacks for the SAP SaaS Provisioning Service
-- How to automatically create APIRule for tenant-specific URL in the Kyma runtime
+- How to automatically create `APIRule` for tenant-specific URL in the Kyma runtime
 
 
 ---
@@ -81,7 +81,7 @@ Payload of subscription PUT and DELETE methods:
 
 [ACCORDION-BEGIN [Step 2: ](Implement Subscription Callbacks)]
 
-A tenant-specific URL should be provided to customers in the onboarding process, at the same time, the URL should be exposed to the Internet as well. Otherwise, customers still cannot access the tenant. URL is exposed in the Kyma runtime through `APIRule`, which needs to be created dynamically through the onboarding/offboarding process using [Kubernetes client for NodeJs](https://github.com/kubernetes-client/javascript).
+A tenant-specific URL should be provided to customers in the onboarding process, at the same time, the URL should be exposed to the Internet as well. Otherwise, customers still cannot access the tenant. URL is exposed in the Kyma runtime through `APIRule`, which needs to be created dynamically through the onboarding/offboarding process using [Kubernetes client for NodeJS](https://github.com/kubernetes-client/javascript).
 
 In the `kyma-multitenant-node/routes/index.js` file, implement the `subscription` and `unsubscription` callbacks. Replace the placeholder with your cluster domain.
 
