😇: Fix grammatical errors

[htinz]

Description

Fixes # [ISSUE]

Type of Change:

• Code
• Quality Assurance
• User Interface
• Outreach
• Documentation

Code/Quality Assurance Only

• Bug fix (non-breaking change which fixes an issue)
• This change requires a documentation update (software upgrade on readme file)
• New feature (non-breaking change which adds functionality pre-approved by mentors)

How Has This Been Tested?

Checklist:

• My PR follows the style guidelines of this project
• I have performed a self-review of my own code or materials
• I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Any dependent changes have been merged
• I have written Kotlin Docs whenever is applicable

Code/Quality Assurance Only

• My changes generate no new warnings
• My PR currently breaks something (fix or feature that would cause existing functionality to not work as expected)
• 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 published in downstream modules

[tinniaru3005]

Hey @htinz . Welcome to Open Souce Hack. Thanks for taking an interest and contributing to this program. But it would be great if you consider a few points while contributing. If you want to work on any issue just check if it is already assigned or not. If the issue is opened and not assigned to anyone ask in the comments and get assigned. After that you can start working on it and once done you can send the PR and get reviewed. While sending the PR link the issue to it. Also, try to stick to the problem addressed in the issue and avoid making extra changes. :)

[htinz]

Hi @tinniaru3005, thank you so much for your comments. Please assign something to me. 😊

[tinniaru3005]

Hi @tinniaru3005, thank you so much for your comments. Please assign something to me. 😊

Hey @htinz . Thanks for your interest in contributing to the community. For contributing you can look to either solve the existing ones or open issues you find. The maintainers will check and add the labels accordingly. But for open source hack, you have to work on the already created issues with the label Open Source Hack. Go to anitab.org. Look at the repositories to find issues with labels as Open Source Hack. If you want to work on them ask in the comments and get assigned. Have a look at the other repositories also for issues. I hope that answers your question. If you have any doubts you can reach us at Zulip chat :)