update workflow version and fix markdownlint

.github/workflows/pull_request.yaml

@@ -7,13 +7,13 @@ on:
 
 jobs:
   qa:
-    uses: stakater/.github/.github/workflows/[email protected].52
+    uses: stakater/.github/.github/workflows/[email protected].62
     with:
       MD_CONFIG: .github/md_config.json
       DOC_SRC: content
       MD_LINT_CONFIG: .markdownlint.yaml
   build:
-    uses: stakater/.github/.github/workflows/[email protected].52
+    uses: stakater/.github/.github/workflows/[email protected].62
     with:
       DOCKER_FILE_PATH: Dockerfile
     secrets:

.github/workflows/push.yaml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   push:
-    uses: stakater/.github/.github/workflows/[email protected].52
+    uses: stakater/.github/.github/workflows/[email protected].62
     with:
       DOCKER_FILE_PATH: Dockerfile
       RELEASE_BRANCH: main

content/external-secret-operator/workflow.md

@@ -16,7 +16,7 @@ Secret Store `tenant-vault-secret-store` is already created in each namespace by
 
 ### Step 3
 
-Service account `tenant-vault-access` being referred by `SecretStore` is already created by Multi Tenant Operator templates. This service account has the `stakater.com/vault-access: 'true'` label, which is used to bound it with the Vault `role` by Multi Tenant Operator. To learn how Multi Tenant Operator authenticates with Vault, see [Vault Multitenancy](https://docs.stakater.com/mto/main/vault-multitenancy.html).
+Service account `tenant-vault-access` being referred by `SecretStore` is already created by Multi Tenant Operator templates. This service account has the `stakater.com/vault-access: 'true'` label, which is used to bound it with the Vault `role` by Multi Tenant Operator. To learn how Multi Tenant Operator authenticates with Vault, see [Vault Multitenancy](https://docs.stakater.com/mto/latest/tutorials/vault/enabling-multi-tenancy-vault.html).
 
 ### Step 4