docs: fix typo in README

[Manice18]

Corrected multiple spelling errors in the README

Description

Please explain the changes you made here.
Explain the motivation for making this change. What existing problem does the pull request solve?

Things to think about before submitting:

• Make sure your changes compile and new tests pass locally.
• Add new tests or update existing ones:
  • A bug fix should include a test that previously would have failed and passes now.
  • New features should come with new tests that exercise and validate the new functionality.
• Extended the README / documentation, if necessary
• Check your code style.
• Write a clear commit title and message
  • The commit message should describe what changed and is targeted at htsjdk developers
  • Breaking changes should be mentioned in the commit message.

[lbergelson]

@Manice18 Thank you!

[Manice18]

@lbergelson i had a small query which is whether your organization will be a part of gsoc this year or not?

[lbergelson]

Is that google summer of code? I don't know of any plans to be part of that. I don't know how that is set up or run. If google wants to pay people to work on htsjdk I think we'd be happy to have their help though :)

[Manice18]

thanks for the info @lbergelson
If your org is taking part then I would be willing to pick your org, if then please guide me through it .