[chore][docs] enable Markdown lint rules MD005 and MD007

.github/pull_request_template.md

@@ -14,6 +14,6 @@
 
 - [ ] I've made sure the tests are passing.
 - Testing Strategy
-   - [ ] Unit tests
-   - [ ] Manual tests
-   - [ ] This PR is not tested :(
+  - [ ] Unit tests
+  - [ ] Manual tests
+  - [ ] This PR is not tested :(

CHANGELOG.md

@@ -293,7 +293,7 @@ The KubeRay 0.5.2 patch release includes the following improvements.
 * Allow watching multiple namespaces
   * [Feature] Watch CR in multiple namespaces with namespaced RBAC resources ([#1106](https://github.com/ray-project/kuberay/pull/1106), [@kevin85421](https://github.com/kevin85421))
 * Autoscaler stability improvements
-   * [Bug] RayService restarts repeatedly with Autoscaler ([#1037](https://github.com/ray-project/kuberay/pull/1037), [@kevin85421](https://github.com/kevin85421))
+  * [Bug] RayService restarts repeatedly with Autoscaler ([#1037](https://github.com/ray-project/kuberay/pull/1037), [@kevin85421](https://github.com/kevin85421))
   * [Bug] autoscaler not working properly in rayjob ([#1064](https://github.com/ray-project/kuberay/pull/1064), [@Yicheng-Lu-llll](https://github.com/Yicheng-Lu-llll))
   * [Bug][Autoscaler] Operator does not remove workers ([#1139](https://github.com/ray-project/kuberay/pull/1139), [@kevin85421](https://github.com/kevin85421))
 

ci/markdownlint.yaml

@@ -2,8 +2,6 @@
 # Default state for all rules
 default: true
 
-MD005: false
-MD007: false
 MD012: false
 MD013: false
 MD022: false

docs/development/release.md

@@ -48,8 +48,8 @@ Bug fix pull requests to fix bugs which found in the documentation testing proce
 
 Manual testing can be time-consuming, and to relieve the workload, we plan to add more CI tests. The minimum requirements to move forward are:
 
-   * All example configurations can work with `kuberay/operator:nightly` and the latest release of Ray (i.e. 2.3.0 for KubeRay v0.5.0).
-   * Update all version strings in the documents.
+* All example configurations can work with `kuberay/operator:nightly` and the latest release of Ray (i.e. 2.3.0 for KubeRay v0.5.0).
+* Update all version strings in the documents.
 
 #### Step 2. Create a new branch in ray-project/kuberay repository
 
@@ -123,8 +123,8 @@ Now, we have the Docker images and Helm charts for v0.5.0.
 #### Step 7. Update KubeRay documentation in Ray repository.
 
 * Update KubeRay documentation in Ray repository with v0.5.0. Examples for v0.5.0:
-    * https://github.com/ray-project/ray/pull/33339
-    * https://github.com/ray-project/ray/pull/34178
+  * https://github.com/ray-project/ray/pull/33339
+  * https://github.com/ray-project/ray/pull/34178
 
 #### Step 8. Generate release
 

docs/guidance/rayclient-nginx-ingress.md

@@ -5,12 +5,12 @@ This document provides an example for connecting Ray client to a Raycluster via
 
 # Requirements
 * Environment:
-    * `Ubuntu`
-    * `Kind`
+  * `Ubuntu`
+  * `Kind`
 
 * Computing resources:
-    * 16GB RAM
-    * 8 CPUs
+  * 16GB RAM
+  * 8 CPUs
 
 ## Step 1: Create a Kind cluster
 The extra arg prepares the Kind cluster for deploying the ingress controller