Update README.md

[karanb01]

I am new to GitHub , Kindly Review the changes , as I am learning Forking, committing and pull request through this.

[AnimeshKumar923]

You're welcome to practice your knowledge through this repo! @karanb01
The changes looks good to me.

Some general things to keep in mind which I've experienced:

• First thing is the PR description that pops in front of you when you open a new PR in any repo. In that description, you should describe what this PR addresses, which issue it resolves (no issue in this case which is fine, minor changes can be directly made without opening issue, but for proposing new ideas or when suggesting major changes you should first open an issue and then a corresponding PR to address that issue) and any more info that may seem relevant.
  By default it fills the description according to the first commit that you've made which I can see is the case with yours.

• Your commit message should describe what changes are being made through each commit. (Although, in this case, it's simple and self-explanatory that you're updating the README file) Sometimes when you're working on more complex PRs, there are times when you should include a good commit message which describes what changes is being made with each PR. That way if you come later and see the commits you get that what exact changes were made through that specific commit, which is helpful in various scenarios.
  It is similar to how you write comments in the code, but this time through Git.

• For example, you can checkout these PRs of mine for reference: 1 2. Take a look on how the commits are being made.

Providing some additional link to docs for better understanding on this matter:

• https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
• https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/best-practices-for-pull-requests#best-practices-for-creating-pull-requests (only read the best practices for creating pull requests section)
• https://cbea.ms/git-commit/
• https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues

These articles should be enough to get started 👍
Hope it helps! Happy contributing! 🙌

[AnimeshKumar923]

@karanb01 what tool are you using to push your changes to GitHub?

[karanb01]

@karanb01 what tool are you using to push your changes to GitHub?

Tools :)....