This is an automated email from the ASF dual-hosted git repository.

DaanHoogland pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack.git


The following commit(s) were added to refs/heads/main by this push:
     new 278bde2442a docs: enable markdownlint rule MD037; standardize 
Markdown; fix typo (#14290)
278bde2442a is described below

commit 278bde2442affe5d893a8eb631b6a72eb66046de
Author: John Bampton <[email protected]>
AuthorDate: Mon Nov 16 21:07:11 2026 +1000

    docs: enable markdownlint rule MD037; standardize Markdown; fix typo 
(#14290)
    
    * docs: enable markdownlint rule MD037; standardize Markdown
    
    Enforce no spaces inside emphasis markers
    
    
https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md037---spaces-inside-emphasis-markers
    
    Clean up and standardize the Markdown and one minor typo fix
    
    * Fixups from code reviews
---
 .github/linters/.markdown-lint.yml | 3 ---
 tools/devcloud4/advanced/README.md | 4 ++--
 tools/devcloud4/basic/README.md    | 4 ++--
 ui/docs/full-test-plan.template.md | 4 ++--
 4 files changed, 6 insertions(+), 9 deletions(-)

diff --git a/.github/linters/.markdown-lint.yml 
b/.github/linters/.markdown-lint.yml
index 6a8a26f4849..2f91a9717b9 100644
--- a/.github/linters/.markdown-lint.yml
+++ b/.github/linters/.markdown-lint.yml
@@ -69,9 +69,6 @@ MD034: false
 # MD036/no-emphasis-as-heading Emphasis used instead of a heading
 MD036: false
 
-# MD037/no-space-in-emphasis Spaces inside emphasis markers
-MD037: false
-
 # MD040/fenced-code-language Fenced code blocks should have a language 
specified
 MD040: false
 
diff --git a/tools/devcloud4/advanced/README.md 
b/tools/devcloud4/advanced/README.md
index 229e9385753..86bb2638be8 100644
--- a/tools/devcloud4/advanced/README.md
+++ b/tools/devcloud4/advanced/README.md
@@ -46,7 +46,7 @@
 vagrant up
 ```
 
-*** Common issues: ***
+***Common issues:***
 
 - 'Cannot forward the specified ports on this VM': There could be MySQL or 
some other
   service running on the host OS causing vagrant to fail setting up local port 
forwarding.
@@ -59,7 +59,7 @@ vagrant up
        git clone https://github.com/apache/cloudstack.git
        ```
 
-       *** Note: ***
+       ***Note:***
 
        Personally I prefer to use the 4.3 codebase rather than main. If you 
wish to do the same:
 
diff --git a/tools/devcloud4/basic/README.md b/tools/devcloud4/basic/README.md
index 91fa81462d6..cba81a492b7 100644
--- a/tools/devcloud4/basic/README.md
+++ b/tools/devcloud4/basic/README.md
@@ -36,7 +36,7 @@
 vagrant up
 ```
 
-*** Common issues: ***
+***Common issues:***
 
 - 'Cannot forward the specified ports on this VM': There could be MySQL or 
some other
   service running on the host OS causing vagrant to fail setting up local port 
forwarding.
@@ -49,7 +49,7 @@ vagrant up
        git clone https://github.com/apache/cloudstack.git
        ```
 
-       *** Note: ***
+       ***Note:***
 
        Personally I prefer to use the 4.3 codebase rather than main. If you 
wish to do the same:
 
diff --git a/ui/docs/full-test-plan.template.md 
b/ui/docs/full-test-plan.template.md
index 259ec5d9858..f978d03e803 100644
--- a/ui/docs/full-test-plan.template.md
+++ b/ui/docs/full-test-plan.template.md
@@ -105,7 +105,7 @@ This requires configuring and setting up CKS: 
https://docs.cloudstack.apache.org
 - [ ] Delete affinity group
 
 **Storage > Volumes**
-- [ ] Basic earch
+- [ ] Basic search
 - [ ] Extended search
 - [ ] Sort
 - [ ] Links
@@ -176,7 +176,7 @@ This requires configuring and setting up CKS: 
https://docs.cloudstack.apache.org
 - [ ] Delete public IP address (only for isolated networks)
 - [ ] Add/delete egress rule (only for isolated networks)
 
-**Network > VPC **
+**Network > VPC**
 - [ ] Basic search
 - [ ] Extended search
 - [ ] Sort

Reply via email to