Enhance README with improvement suggestions

[Dippp10-ally]

PR Title

docs: improve README formatting and structure

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (code restructuring without changing functionality)
• Documentation update
• Performance improvement
• Security patch

---

Description

This PR improves the project's README by enhancing its formatting, organization, and overall readability. The documentation has been restructured with clearer headings, better section flow, and improved consistency, making it easier for contributors and users to understand the project, installation process, usage instructions, and contribution guidelines.

---

Related Issue

Closes #122

---

Changes Made

• Improved the overall README structure and section hierarchy.
• Standardized heading styles and formatting.
• Enhanced installation and usage instructions for better clarity.
• Organized contributor and project information into logical sections.
• Fixed formatting inconsistencies, spacing, and markdown styling.
• Corrected grammar, wording, and minor documentation issues.
• Improved readability for both new users and contributors.

---

Screenshots

Before

After

---

Testing

How has this been tested?

• Manual testing completed
• Tested on Desktop (Chrome, Firefox, Safari)
• Tested on Mobile (iOS Safari, Chrome Mobile)
• Tested on Tablet
• Added new unit tests
• All existing tests pass

Test Scenarios

1. Verified that all Markdown renders correctly on GitHub.
2. Checked that headings, lists, links, and formatting display properly across the README.

---

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have checked my code and corrected any misspellings
• My commit messages follow the Conventional Commits specification

---

Frontend Changes (if applicable)

• TypeScript types are properly defined
• Component uses Tailwind CSS (no inline styles)
• Responsive design tested on multiple screen sizes
• Accessibility (ARIA labels, keyboard navigation) considered
• Dark mode compatibility verified

---

Backend Changes (if applicable)

• Follows PEP 8 style guide
• Database migrations created (if schema changed)
• API endpoint documentation updated
• Input validation implemented
• Security best practices followed
• No sensitive data logged

---

Security Considerations

Does this PR introduce any security concerns?

• No security impact
• Security review required
• Handles sensitive data (encryption implemented)
• Changes authentication/authorization logic
• Adds new external dependencies

---

Breaking Changes

Does this PR introduce breaking changes?

• No
• Yes (describe below)

---

Additional Notes

This PR focuses solely on documentation improvements. No source code or application functionality has been modified.

---

Deployment Notes

• No special steps needed
• Environment variables need updating
• Database migration required
• Cache needs clearing
• Other: ___

[vercel]

@Dippp10-ally is attempting to deploy a commit to the pankaj-bind's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Dippp10-ally]

@pankaj-bind ji , do assign labels called as gssoc:approved , level:intermediate , type:docs , quality:exceptional to above pull request number 123 also.....do merge above pull request number 123 also.....