Fixed grammatical mistakes

DESIGN_CONTRIBUTION_GUIDELINES.md

@@ -16,11 +16,11 @@ Open Source Ambassadors is at least half year contribution program organised by
 
 ## General Responsibilities
 
-- Attend product roadmap in assigned project
-- Review existing designs
-- Design new feature, redesign existing features (if ticket exist and assigned)
-- Create and maintain metrics document and guard consistency in the project
-- Review UI coding PR’s (test if everything looks as expected)
-- Attend design session to discuss challenges in design within our projects
-- Create User Journey wireframes
-- Meet on a monthly basis, with all designers to discuss processes
+- Attend product roadmap in assigned project.
+- Review existing designs.
+- Design new feature, redesign existing features (if ticket exist and assigned).
+- Create and maintain metrics document and guard consistency in the project.
+- Review UI coding PR’s (test if everything looks as expected).
+- Attend design session to discuss challenges in design within our projects.
+- Create User Journey wireframes.
+- Meet on a monthly basis, with all designers to discuss processes.

README.md

@@ -8,14 +8,14 @@ If you are here, it probably means you are either looking for a place to start c
 
 ## Contributing
 
-We are glad to know that you would like to contribute to our open source projects. If you are new to our community, we strongly recommend getting through the following list.
+We are glad to know that you would like to contribute to our open source projects. If you are new to our community, we strongly recommend getting through the following lists.
   - Read through the [Code of Conduct](/Contributing/CODE_OF_CONDUCT.md) and [Reporting Guidelines](/Contributing/REPORTING_GUIDELINES.md)
   - Join our [Zulip](http://anitab-org.zulipchat.com) community to read our discussions and be part of them! Learn more about how we use Zulip [here](/zulip.md).
   - Attend our Open Community sessions to interact with community members and ask questions. You can check our calendars here: [PST](https://calendar.google.com/calendar/embed?src=sh10tv3mtfve62somg9nngp9tg%40group.calendar.google.com&ctz=America/Los_Angeles) || [EST](https://calendar.google.com/calendar/embed?src=sh10tv3mtfve62somg9nngp9tg%40group.calendar.google.com&ctz=America/New_York) || [GMT](https://calendar.google.com/calendar/embed?src=sh10tv3mtfve62somg9nngp9tg%40group.calendar.google.com&ctz=GMT) || [WAT](https://calendar.google.com/calendar/embed?src=sh10tv3mtfve62somg9nngp9tg%40group.calendar.google.com&ctz=Africa/Lagos) || [IST](https://calendar.google.com/calendar/embed?src=sh10tv3mtfve62somg9nngp9tg%40group.calendar.google.com&ctz=Asia/Colombo) || [AEDT](https://calendar.google.com/calendar/embed?src=sh10tv3mtfve62somg9nngp9tg%40group.calendar.google.com&ctz=Australia/Sydney)
 
 ## Documentation
 
-Below is a list of documents currently in this repository. If none of these documentation helps, feel free to reach out to us either by asking your question on Zulip or creating an issue requesting the information you need.
+Below is a list of documents currently in this repository. If none of these documentations helps, feel free to reach out to us either by asking your question on Zulip or creating an issue requesting the information you need.
 
 - [Ways to contribute to our community](/ways-to-contribute.md)
 - [Our AnitaB.org Open Source Blog publication](/our-blog.md)

frequently-asked-questions.md

@@ -71,7 +71,7 @@ A: No, you do not have to be a part of open source teams to contribute to AnitaB
 A: We rebranded from Systers Open Source to AnitaB.org Open Source in 2020. GitHub projects that were active or still needed development have been moved to [github.com/anitab-org](http://github.com/anitab-org). 
 
 **Q: Are we still using Systers-open source on Slack?**
-A: Nope, we moved to Zulip - [AnitaB-org.zulipchat.com](https://anitab-org.zulipchat.com/) and anyone who was in our Slack was invited to the new workspace.
+A: Nope, we moved to Zulip - [AnitaB-org.zulipchat.com](https://anitab-org.zulipchat.com/) and those who were in our Slack were invited to the new workspace.
 
 **Q: Why did we move from Slack to Zulip?**
 A: Here are some reasons:

our-blog.md

@@ -43,7 +43,7 @@ Make sure to provide us with following details:
 3. Select "Add to publication" option;
 4. Select the AnitaB.org Open Source (you will see this in case you are a writer);
     <img src="https://user-images.githubusercontent.com/11148726/87883600-78940a00-ca00-11ea-9534-49eabeff2f16.png" alt="AnitaB.org open source option in the dropdown" width="600"/>
-5. Click submit!
+5. Click submit 
 
 **References:**
 - [Add a draft or post to publication](https://help.medium.com/hc/en-us/articles/213904978-Add-a-draft-or-post-to-publication) on Medium

quality-assurance.md

@@ -88,11 +88,11 @@
 1. Choose a test scenario in the project you’ve chosen and execute it on either the PR or deployed version that is being tested.
    * Open issues under the respective github repo if you find any bugs.
 
-2. Search on TestQuality if the Test Case is already documented. If not, document the testcase on TestQuality under the respective Test Plan and Test Suite. Here is a [demo](https://drive.google.com/file/d/1pkxCAPR9G3lYjUf_Ym8bmuglDWBdEU2c/view?usp=sharing).
+2. Search on Test Quality if the Test Case is already documented. If not, document the testcase on TestQuality under the respective Test Plan and Test Suite. Here is a [demo](https://drive.google.com/file/d/1pkxCAPR9G3lYjUf_Ym8bmuglDWBdEU2c/view?usp=sharing).
    * Have the Test Case reviewed by another QA team member.
 
 3. (Optional) Automate the Test Case, for example: [Mentorship Backend User Journey](https://github.com/anitab-org/mentorship-backend/pull/708).
 
 4. If you decide to skip step 3, search if there is an existing issue to automate that test case. If not, open an issue with label `Quality Assurance`.
 
-5. If you automate a Test case make sure you mark it as `Automated` on TestQuality.
+5. If you automate a Test case make sure you mark it as `Automated` on Test Quality.