fix cspell and links checks (#912)

* fix cspell and links checks

* Change list to enable linters instead of disable

* fix megalinter version

* Fix cspell

* Fix cspell and links

* revert link change

* [MegaLinter] Apply linters fixes

* revert fix

* fix cspell

Co-authored-by: shiranr <[email protected]>

Author: shiranr

.cspell.json

@@ -25,8 +25,12 @@
     "Aridhia",
     "Asana",
     "Autopep",
+    "authpassword",
     "Autowire",
+    "appconfig",
     "Azul",
+    "azurem",
+    "azurerm",
     "BYOK",
     "Bekso",
     "Bytedance",
@@ -38,12 +42,14 @@
     "CUDA",
     "CUITs",
     "Checkstyle",
+    "CICD",
     "Cloudsploit",
     "Cobertura",
     "Conda",
     "Craftspersonship",
     "DARPA",
     "DAST",
+    "datascience",
     "DBFS",
     "Databricks",
     "Dataverse",
@@ -58,7 +64,6 @@
     "FHEW",
     "FHIR",
     "FIPS",
-    "Failureas",
     "Fairlearn",
     "Falco",
     "Federica",
@@ -91,6 +96,9 @@
     "Kubes",
     "Kustomization",
     "Kustomize",
+    "keyvault",
+    "Keyvault",
+    "kvsecret",
     "Kyverno",
     "LINQ",
     "LLDB",
@@ -321,6 +329,7 @@
     "noninteractive",
     "nonoptimal",
     "nswag",
+    "NPMJS",
     "omnisharp",
     "opensource",
     "opentelemetry",
@@ -373,6 +382,7 @@
     "securability",
     "serializability",
     "setvariable",
+    "servicename",
     "shellcheck",
     "shfmt",
     "shunit",
@@ -417,18 +427,25 @@
     "webservice",
     "websockets",
     "westus",
+    "westeurope",
     "winget",
     "workstream",
     "worspace",
     "yapf",
     "zstd",
     "Apdex",
     "Aur\u00e9lien",
-    "Avi",
-    "zienis",
+    "Avizienis",
     "Customizabile",
+    "CHECKOV",
     "Dodd's",
-    "G\u00e9ron's"
+    "Dodd’s",
+    "G\u00e9ron's",
+    "bugbug",
+    "Bitnami",
+    "Kubeseal",
+    "KSOPS",
+    "OTLP"
   ],
   "version": "0.2"
 }

.mega-linter.yml

@@ -3,17 +3,16 @@
 
 APPLY_FIXES: all # all, none, or list of linter keys
 # ENABLE: # If you use ENABLE variable, all other languages/formats/tooling-formats will be disabled by default
-# ENABLE_LINTERS: # If you use ENABLE_LINTERS variable, all other linters will be disabled by default
-DISABLE:
-  - COPYPASTE # Comment to enable checks of excessive copy-pastes
-  - HTML
-  - DOCKERFILE
-  - JSON
-DISABLE_LINTERS:
-  - REPOSITORY_CHECKOV
-  - REPOSITORY_GITLEAKS
-  - SPELL_MISSPELL
-  - YAML_V8R
+ENABLE_LINTERS:
+  - ACTION_ACTIONLINT
+  - MARKDOWN_MARKDOWNLINT
+  - MARKDOWN_MARKDOWN_LINK_CHECK
+  - MARKDOWN_MARKDOWN_TABLE_FORMATTER
+  - REPOSITORY_SECRETLINT
+  - SPELL_CSPELL
+  - YAML_PRETTIER
+  - YAML_YAMLLINT
+
 SPELL_CSPELL_DISABLE_ERRORS: true
 SHOW_ELAPSED_TIME: true
 FILEIO_REPORTER: false

.projector/workItemTemplates/kubernetes-at-the-edge.yml

@@ -21,7 +21,7 @@ items:
                 description: Understand what workloads will be running on the cluster and the compute requirements including any requirements for mixed clusters (OS, cpu, mem, etc.)
               - name: Evaluate compute options
                 type: task
-                description: Reference this [trade-off doc](https://docs.microsoft.com/azure/architecture/operator-guides/aks/choose-kubernetes-edge-compute-option) to help evaluate trade-offs between bare-metal kubernetes, kubernetes on Azure Stack Edge, and AKS on Azure Stack HCI.
+                description: Reference this [trade-off doc](https://learn.microsoft.com/azure/architecture/operator-guides/aks/choose-kubernetes-edge-compute-option) to help evaluate trade-offs between bare-metal kubernetes, kubernetes on Azure Stack Edge, and AKS on Azure Stack HCI.
               - name: If applicable, evaluate virtualization options
                 type: task
                 description: In the case of bare-metal, you will likely leverage virtualization of host systems. Look into what options are available for the respective host and evaluate against requirements
@@ -98,7 +98,7 @@ items:
             children:
               - name: Identify tooling to be used to spin up Kubernetes
                 type: task
-                description: For baremetal clusters, reference this [decision-tree](https://docs.microsoft.com/azure/architecture/operator-guides/aks/choose-bare-metal-kubernetes) to determine which tooling shall be used
+                description: For baremetal clusters, reference this [decision-tree](https://learn.microsoft.com/azure/architecture/operator-guides/aks/choose-bare-metal-kubernetes) to determine which tooling shall be used
           - name: As a cluster operator, I want to leverage existing tools (AzDO, Ansible or cluster api) to configure my clusters so that configuration may be repeatable and scalable. Note, in cases where cluster setup requires a lot of manual coordination, it's important to determine how to automate and manage configuration such that clusters can be configured at scale
             type: story
             acceptanceCriteria:
@@ -115,7 +115,7 @@ items:
             type: story
             acceptanceCriteria:
               - Tests implemented in pipeline to ensure health of clusters post updates
-          - name: As a cluster operator, I want to use a tool like azure arc for k8s (https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/) so that I can manage multiple clusters from a single pane of glass
+          - name: As a cluster operator, I want to use a tool like azure arc for k8s (https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/) so that I can manage multiple clusters from a single pane of glass
             type: story
             acceptanceCriteria:
               - Decision record documenting requirements of single pane view, alternative considerations, and chosen tooling

docs/SPRINT-STRUCTURE.md

@@ -20,7 +20,7 @@ The purpose of this document is to:
   - Add [README.md](resources/templates/README.md), [LICENSE](resources/templates/LICENSE), [CONTRIBUTING.md](resources/templates/CONTRIBUTING.md), .gitignore, etc
 - [ ] [Build a Product Backlog](agile-development/advanced-topics/backlog-management/README.md)
   - Set up a project in your chosen project management tool (ex. Azure DevOps)
-  - [INVEST](<https://en.wikipedia.org/wiki/INVEST_(mnemonic)>) in good User Stories and Acceptance Criteria
+  - [INVEST](https://en.wikipedia.org/wiki/INVEST_(mnemonic)) in good User Stories and Acceptance Criteria
   - [Non-Functional Requirements Guidance](design/design-patterns/non-functional-requirements-capture-guide.md)
 
 ### Day 1

docs/accessibility/README.md

@@ -4,7 +4,7 @@ Accessibility is a critical component of any successful project and ensures the
 
 ## Getting Started
 
-If you are new to accessibility or are looking for an overview of accessibility fundamentals, Microsoft Learn offers a great training course that covers a broad range of topics from creating accessible content in Office to designing accessibility features in your own apps. You can learn more about the course or get started at [Microsoft Learn: Accessibility Fundamentals](https://docs.microsoft.com/en-us/learn/paths/accessibility-fundamentals/).
+If you are new to accessibility or are looking for an overview of accessibility fundamentals, Microsoft Learn offers a great training course that covers a broad range of topics from creating accessible content in Office to designing accessibility features in your own apps. You can learn more about the course or get started at [Microsoft Learn: Accessibility Fundamentals](https://learn.microsoft.com/en-us/learn/paths/accessibility-fundamentals/).
 
 ## Accessibility Insights
 

docs/agile-development/advanced-topics/collaboration/add-pairing-field-azure-devops-cards.md

@@ -1,16 +1,16 @@
 # How to add a Pairing Custom Field in Azure DevOps User Stories
 
-This document outlines the benefits of adding a custom field of type _Identity_ in [Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/user-guide/what-is-azure-devops) user stories, prerequisites, and a step-by-step guide.
+This document outlines the benefits of adding a custom field of type _Identity_ in [Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/user-guide/what-is-azure-devops) user stories, prerequisites, and a step-by-step guide.
 
 ## Benefits of adding a custom field
 
 Having the names of both individuals [pairing on a story](README.md) visible on the Azure DevOps cards can be helpful during sprint ceremonies and lead to greater accountability by the pairing assignee. For example, it is easier to keep track of the individuals assigned stories as part of a pair during sprint planning by using the "pairing names" field. During stand-up it can also help the Process Lead filter stories assigned to the individual (both as an owner or as a pairing assignee) and show these on the board. Furthermore, the pairing field can provide an additional data point for reports and burndown rates.
 
 ## Prerequisites
 
-Prior to customizing Azure DevOps, review [Configure and customize Azure Boards](https://docs.microsoft.com/en-us/azure/devops/boards/configure-customize).
+Prior to customizing Azure DevOps, review [Configure and customize Azure Boards](https://learn.microsoft.com/en-us/azure/devops/boards/configure-customize).
 
-In order to add a custom field to user stories in Azure DevOps changes must be made as an **Organizational setting**. This document therefore assumes use of an existing Organization in Azure DevOps and that the user account used to make these changes is a member of the [Project Collection Administrators Group](https://docs.microsoft.com/en-us/azure/devops/organizations/security/set-project-collection-level-permissions).
+In order to add a custom field to user stories in Azure DevOps changes must be made as an **Organizational setting**. This document therefore assumes use of an existing Organization in Azure DevOps and that the user account used to make these changes is a member of the [Project Collection Administrators Group](https://learn.microsoft.com/en-us/azure/devops/organizations/security/set-project-collection-level-permissions).
 
 ### Change the organization settings
 

docs/agile-development/advanced-topics/effective-organization/delivery-plan.md

@@ -42,6 +42,6 @@ Step 4: Based on your capacity, you know have the options
 
 You can also leverage one of these tools by creating your epics and features and add the weeks estimates.
 
-The [Plans (Preview) feature on Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/project/navigation/preview-features?view=azure-devops) will help you make a plan. Delivery Plans provide a schedule of stories or features your team plan to deliver. Delivery Plans show the scheduled work items by a sprint (iteration path) of selected teams against a calendar view.
+The [Plans (Preview) feature on Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/project/navigation/preview-features?view=azure-devops) will help you make a plan. Delivery Plans provide a schedule of stories or features your team plan to deliver. Delivery Plans show the scheduled work items by a sprint (iteration path) of selected teams against a calendar view.
 
 Confluence JIRA, Trello, Rally, Asana, Basecamp, and GitHub Issues are other similar tools in the market (some are free, others you pay a monthly fee, or you can install on-prem) that you can leverage.

docs/agile-development/advanced-topics/team-agreements/definition-of-ready.md

@@ -6,7 +6,7 @@ When the development team picks a user story from the top of the backlog, the us
 
 ## What it is
 
-*Definition of Ready* is the agreement made by the scrum team around how complete a user story should be in order to be selected as candidate for estimation in the sprint planning. These can be codified as a checklist in user stories using [GitHub Issue Templates](https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository) or [Azure DevOps Work Item Templates](https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/work-item-template?view=azure-devops&tabs=browser).
+*Definition of Ready* is the agreement made by the scrum team around how complete a user story should be in order to be selected as candidate for estimation in the sprint planning. These can be codified as a checklist in user stories using [GitHub Issue Templates](https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository) or [Azure DevOps Work Item Templates](https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/work-item-template?view=azure-devops&tabs=browser).
 
 It can be understood as a checklist that helps the Product Owner to ensure that the user story they wrote contains all the necessary details for the scrum team to understand the work to be done.
 

docs/agile-development/basics/Backlog Management/README.md

@@ -4,7 +4,7 @@ This section has links directing you to best practices for managing Product and
 
 - [Product Backlog](https://scrumguides.org/scrum-guide.html#product-backlog 'Product Backlog')
 - [Sprint Backlog](https://scrumguides.org/scrum-guide.html#sprint-backlog 'Sprint Backlog')
-- [Acceptance Criteria](https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/best-practices-product-backlog?view=azure-devops#acceptance-criteria 'Acceptance Criteria')
+- [Acceptance Criteria](https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/best-practices-product-backlog?view=azure-devops#acceptance-criteria 'Acceptance Criteria')
 - [Definition of Done](https://scrumguides.org/scrum-guide.html#increment 'Definition of Done')
 - [Definition of Ready](https://www.scrum.org/resources/blog/walking-through-definition-ready 'Definition of Ready')
 - [Estimation Basics in Agile](https://www.scrum.org/resources/blog/what-scrum-says-about-estimates 'Estimation Basics in Agile')

docs/agile-development/basics/Ceremonies/README.md

@@ -3,7 +3,7 @@
 This section has links directing you to best practices for conducting the Agile ceremonies.  After reading through the best practices you should have a basic understanding of the key Agile ceremonies in terms of purpose, value and best practices around conducting and facilitating these ceremonies.
 
 - [Planning](https://scrumguides.org/scrum-guide.html#sprint-planning 'Sprint Planning')
-- [Refinement](https://docs.microsoft.com/devops/plan/what-is-agile-development#diligent-backlog-refinement 'Refinement')
+- [Refinement](https://learn.microsoft.com/devops/plan/what-is-agile-development#diligent-backlog-refinement 'Refinement')
 - [Retrospective](https://scrumguides.org/scrum-guide.html#sprint-retrospective 'Retrospective')
 - [Sprint Review/Demo](https://scrumguides.org/scrum-guide.html#sprint-review 'Sprint Review')
 - [Stand-Up/Daily Scrum](https://scrumguides.org/scrum-guide.html#daily-scrum 'Stand-up/Daily Scrum')

docs/agile-development/basics/README.md

@@ -2,8 +2,8 @@
 
 If you are new to Agile development or if you are looking for a refresher, this section will provides links to information that provide best pracices for Backlog Management, Agile Ceremonies, Roles within Agile and Agile Sprints.
 
-- [What is Agile](https://docs.microsoft.com/en-us/devops/plan/what-is-agile 'What is Agile')
-- [What is Agile Development](https://docs.microsoft.com/en-us/devops/plan/what-is-agile-development 'What is Agile Development')
+- [What is Agile](https://learn.microsoft.com/en-us/devops/plan/what-is-agile 'What is Agile')
+- [What is Agile Development](https://learn.microsoft.com/en-us/devops/plan/what-is-agile-development 'What is Agile Development')
 - [Backlog Management](./Backlog%20Management/)
 - [Ceremonies](./Ceremonies/)
 - [Roles](./Roles/)

docs/agile-development/basics/Sprints/README.md

@@ -2,7 +2,7 @@
 
 This section has links directing you to best practices in regards to what a sprint is within agile and the practices around the sprint.  After reading through the best practices you should have a basic understanding of Sprint Planning and the Sprint Backlog, Sprint Execution and the Daily Standup, Sprint Review and Sprint Retrospective and the key output of the sprint which is called the Increment.
 
-- [Sprint Planning and the Sprint Backlog](https://docs.microsoft.com/en-us/devops/plan/what-is-scrum#sprint-planning-and-the-sprint-backlog 'Sprint Planning and Sprint Backlog')
-- [Sprint Execution and the Daily Standup](https://docs.microsoft.com/en-us/devops/plan/what-is-scrum#sprint-execution-and-daily-scrum 'Sprint Execution and the Daily Standup')
-- [Sprint Review and Sprint Retrospective](https://docs.microsoft.com/en-us/devops/plan/what-is-scrum#sprint-review-and-sprint-retrospective 'Sprint Review and Sprint Retrospective')
-- [Increment](https://docs.microsoft.com/en-us/devops/plan/what-is-scrum#increment 'Increment')
+- [Sprint Planning and the Sprint Backlog](https://learn.microsoft.com/en-us/devops/plan/what-is-scrum#sprint-planning-and-the-sprint-backlog 'Sprint Planning and Sprint Backlog')
+- [Sprint Execution and the Daily Standup](https://learn.microsoft.com/en-us/devops/plan/what-is-scrum#sprint-execution-and-daily-scrum 'Sprint Execution and the Daily Standup')
+- [Sprint Review and Sprint Retrospective](https://learn.microsoft.com/en-us/devops/plan/what-is-scrum#sprint-review-and-sprint-retrospective 'Sprint Review and Sprint Retrospective')
+- [Increment](https://learn.microsoft.com/en-us/devops/plan/what-is-scrum#increment 'Increment')

docs/automated-testing/e2e-testing/recipes/gauge-framework.md

@@ -186,11 +186,14 @@ This section gives specific instructions on setting up Gauge in a macOS environm
    if HomeBrew is working properly, you should see something similar to the following:
 
 ```bash
-==> Downloading https://homebrew.bintray.com/bottles/gauge-1.0.6.mojave.bottle.tar.gz
-==> Downloading from https://akamai.bintray.com/45/45b496b39ee682a95ca49b36a94e8041e03fca3644e80223c36539f495fee384?__gda__=exp=1568017021~hmac=f6ca3a9
+==> Fetching gauge
+==> Downloading https://ghcr.io/v2/homebrew/core/gauge/manifests/1.4.3
 ######################################################################## 100.0%
-==> Pouring gauge-1.0.6.mojave.bottle.tar.gz
-🍺  /usr/local/Cellar/gauge/1.0.6: 3 files, 18.5MB
+==> Downloading https://ghcr.io/v2/homebrew/core/gauge/blobs/sha256:05117bb3c0b2efeafe41e817cd3ad86307c1d2ea7e0e835655c4b51ab2472893
+==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:05117bb3c0b2efeafe41e817cd3ad86307c1d2ea7e0e835655c4b51ab2472893?se=2022-12-13T12%3A35%3A00Z&sig=I78SuuwNgSMFoBTT
+######################################################################## 100.0%
+==> Pouring gauge--1.4.3.ventura.bottle.tar.gz
+    /usr/local/Cellar/gauge/1.4.3: 6 files, 18.9MB
 ```
 
 ### Step 2 : Installing Gauge extension for Visual Studio Code