Update README.md

[Drashish987]

What has changed?

Improved formatting and clarity in the README.md file:

. Fixed grammar in the Note section

. Converted Technology Stack section into a more readable bullet list

. Added a tip for running the local development server

This PR Resolves #(issue)

Type of change

Please delete options that are not relevant.

• 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).
• Documentation update (if none of the other choices apply).

How Has This Been Tested?

No code changes — this is a documentation-only update.
Previewed README changes using GitHub's markdown preview.

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.

[github-actions]

Thank you and congratulations 🎉 for opening your very first pull request in keploy

[Drashish987]

Hi! This PR is ready for review. Could someone with write access please approve the workflows and provide a review? Thanks!

[Drashish987]

Hi @nehagup 👋, could you please review this PR when you get a chance? Thank you!

[pratik-mahalle]

Hi @Drashish987, Thank you raising the pr. Unfortunately we can`t merge this as it is just README change and it does not include any relevant changes. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized.
This being a part of an assignment in api fellowship would be counted since you were suppsoed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

[Drashish987]

Hi @Drashish987, Thank you raising the pr. Unfortunately we can`t merge this as it is just README change and it does not include any relevant changes. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized.
This being a part of an assignment in api fellowship would be counted since you were suppsoed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

Thank you for reviewing my PR and for the clarification. I completely understand the importance of maintaining relevance and quality in contributions to the repository.

Since this was part of the API Fellowship assignment, I went ahead and created the PR as instructed, but I fully respect your decision not to merge it given the scope of the change.

I appreciate your feedback, and I’ll make sure to contribute more substantial updates or issue resolutions in the future.

Thanks again for your time and guidance.

Best regards,
@Drashish98