-
Notifications
You must be signed in to change notification settings - Fork 243
docs: fix grammar and improve clarity in Testing Guide documentation #675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Remove negative margins (-ml-2, -ml-0.5) causing misalignment - Increase padding from p-4 to p-6 for better spacing - Fix typo: Question? -> Questions? - Remove unnecessary ml-0 class - Enhance visual consistency and proper alignment Signed-off-by: Kartikey Gupta <[email protected]>
Signed-off-by: Kartikey Gupta <[email protected]>
Signed-off-by: Kartikey Gupta <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes grammar and style issues in the "Testing Guide" documentation across multiple versions. The changes improve readability and consistency by correcting capitalization, sentence structure, and punctuation throughout the documentation.
- Fixed title capitalization from "testing Guide" to "Testing Guide"
- Improved sentence clarity and grammar throughout the content
- Enhanced consistency in product name capitalization (Keploy)
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
File | Description |
---|---|
versioned_docs/version-3.0.0/keploy-explained/testing-guide.md | Grammar and style improvements to the Testing Guide documentation |
versioned_docs/version-2.0.0/keploy-explained/testing-guide.md | Same grammar and style improvements applied to version 2.0.0 |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
I have fixed it, please once go through it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the changes @kartikeyg0104!
This looks good to me @Achanandhi-M
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @kartikeyg0104 can you please add the npm run build output in the PR description and also can you please update the PR title and description?
Okay sir, will do it. |
SIr, I have done the changes. |
Signed-off-by: Kartikey Gupta <[email protected]>
@Achanandhi-M Sir, Is anything else have to be done? |
What has changed?
Type of change
Screenshots
How Has This Been Tested?
npm run build
andnpm run serve
.Checklist:
npm run build output
[SUCCESS] Generated static files in "build".$USER:$ (id -gn $USER) /Users/kartikey0104/.config │
[INFO] Use
npm run serve
command to test your build locally.┌─────────────────────────────────────────────────────────────────┐
│ @docusaurus/core update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R