Enhance README with improvement suggestions#361
Open
Dippp10-ally wants to merge 1 commit into
Open
Conversation
Add improvement notes for README formatting and structure.
|
@Dippp10-ally is attempting to deploy a commit to the Lovely Mahour's projects Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
@lovelymahor ji , do assign labels called as gssoc:approved , level:intermediate , type:docs , quality:exceptional to above pull request number 361...do merge above pull request number 361 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📝 Pull Request
📌 Description
This PR improves the formatting and structure of the
README.mdto enhance readability, organization, and contributor onboarding experience.✨ Changes Made
🔗 Related Issue
Closes #360
🏷️ Type of Change
📸 Screenshots (if applicable)
✅ Checklist
🧪 Testing
📋 Additional Notes
This PR only improves documentation formatting and structure.
No functional or backend code changes were introduced.