Fix heading formatting and remove horizontal lines in installation.md #402
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: suntiwari3495-arch <[email protected]>
codeEvolveZenith345
requested review from
divya-mohan0209,
k8s-dev and
ksatchit
as code owners
✅ Deploy Preview for docs-litmuschaos ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PriteshKiri
approved these changes
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR fixes formatting inconsistencies in the Installation documentation by:
**) from 5 headings to ensure proper rendering---) before the "Verify your installation" and "Accessing the ChaosCenter" sectionsThese changes improve the documentation's visual consistency and follow standard Markdown formatting conventions.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #355Special notes for your reviewer:
All changes are purely formatting-related with no content modifications. The changes include:
**bold markers)Checklist:
documentationtag