[MegaLinter] Apply linters fixes

Author: nvuillam

docs/descriptors/json_eslint_plugin_jsonc.md

@@ -15,7 +15,7 @@ description: How to use eslint-plugin-jsonc (configure, ignore files, ignore err
 
 _This linter has been disabled in this version_
 
-_Disabled reason: Bug in eslint-plugin-jsonc: https://github.com/ota-meshi/eslint-plugin-jsonc/issues/328_
+_Disabled reason: Bug in eslint-plugin-jsonc: <https://github.com/ota-meshi/eslint-plugin-jsonc/issues/328>_
 
 **eslint-plugin-jsonc** uses eslint to lint [**json**](https://www.json.org/), [**jsonc**](https://github.com/microsoft/node-jsonc-parser) and [**json5**](https://json5.org/) (extended JSON with comments & more).
 

docs/descriptors/makefile_checkmake.md

@@ -9,7 +9,7 @@ description: How to use checkmake (configure, ignore files, ignore errors, help
 
 _This linter has been disabled in this version_
 
-_Disabled reason: Security issues: https://github.com/checkmake/checkmake/issues/99_
+_Disabled reason: Security issues: <https://github.com/checkmake/checkmake/issues/99>_
 
 **checkmake** is a linter for Makefiles that helps enforce best practices and identify common issues in Makefile syntax and structure. It helps prevent common Makefile pitfalls and makes build processes more reliable and maintainable.
 

docs/descriptors/markdown_remark_lint.md

@@ -9,7 +9,7 @@ description: How to use remark-lint (configure, ignore files, ignore errors, hel
 
 _This linter has been disabled in this version_
 
-_Disabled reason: Bug in remark-lint: https://github.com/remarkjs/remark-lint/issues/322_
+_Disabled reason: Bug in remark-lint: <https://github.com/remarkjs/remark-lint/issues/322>_
 
 **remark-lint** is a powerful plugin for the remark markdown processor that provides comprehensive linting and formatting capabilities for Markdown files. Built on the unified collective's remark ecosystem, it offers extensive rule-based validation with automatic fixing capabilities and a rich plugin architecture for customized Markdown processing workflows.
 

docs/descriptors/repository_gitleaks.md

@@ -33,17 +33,17 @@ description: How to use gitleaks (configure, ignore files, ignore errors, help &
 If MegaLinter with gitleaks runs against a PR on a platform not listed above, analysis is performed on the whole repository (this is the default gitleaks behavior; the commits scanned depend on the fetch-depth configuration).
 
 You can still choose to scan only PR commits in your CI/CD platform by setting the following MegaLinter environment variables:
-  - `PULL_REQUEST=true`\*
-  - `REPOSITORY_GITLEAKS_PR_COMMITS_SCAN: true`
-  - `REPOSITORY_GITLEAKS_PR_SOURCE_SHA` with last commit sha from your PR and `REPOSITORY_GITLEAKS_PR_TARGET_SHA` commit sha from your target branch (for example, `main` if you do PR to main branch)
+- `PULL_REQUEST=true`\*
+- `REPOSITORY_GITLEAKS_PR_COMMITS_SCAN: true`
+- `REPOSITORY_GITLEAKS_PR_SOURCE_SHA` with last commit sha from your PR and `REPOSITORY_GITLEAKS_PR_TARGET_SHA` commit sha from your target branch (for example, `main` if you do PR to main branch)
 
     Example commands:
-      - Source commit SHA:
+  - Source commit SHA:
         ```bash
         git rev-list -n 1 refs/remotes/origin/<source_branch>
         ```
 
-      - Target commit SHA:
+  - Target commit SHA:
         ```bash
         git rev-parse refs/remotes/origin/<target_branch>
         ```

docs/descriptors/salesforce_lightning_flow_scanner.md

@@ -15,7 +15,7 @@ description: How to use lightning-flow-scanner (configure, ignore files, ignore
 
 _This linter has been disabled in this version_
 
-_Disabled reason: Repo archived -> https://github.com/Lightning-Flow-Scanner_
+_Disabled reason: Repo archived -> <https://github.com/Lightning-Flow-Scanner>_
 
 **Lightning Flow Scanner** is a specialized SFDX plugin that analyzes Salesforce Flows for integrity issues, performance problems, and adherence to best practices. It helps developers build reliable and maintainable Flow automations.