Improve README formatting and structure suggestions

[Dippp10-ally]

Description

Enhanced the README by adding formatting recommendations and a suggested structure to improve readability, navigation, and contributor onboarding. These changes focus on documentation quality and project presentation without modifying application functionality.

Related Issue

Closes #181

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 causes existing functionality to change)
• Documentation update
• Refactor
• Performance improvement

Changes Made

• Added recommendations for improved README organization and section hierarchy.
• Suggested consistent formatting practices for headings, lists, and code blocks.
• Included guidance for sections such as Installation, Features, Usage, Contributing, and License.
• Improved documentation clarity to make the project more approachable for new contributors.
• Added notes to enhance overall readability and maintainability.

Testing

• Ran npm test — all tests pass
• Tested manually (if applicable)

Documentation changes were reviewed to ensure formatting consistency and markdown compatibility.

Screenshots (if applicable)

N/A – Documentation-only changes.

Checklist

• My code follows the project's code style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have updated the documentation if necessary
• My changes are scoped to a single issue

[vercel]

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

A member of the Team first needs to authorize it.

[Dippp10-ally]

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