Fix some grammar and vocabs mistakes

README.md

@@ -1,30 +1,30 @@
 # Mozilla and GSoC 2020
 
-I'm pleased to announce that Mozilla has been accepted as a mentoring organization in the 2020 Google Summer Of Code, and would like express our gratitude to everyone on the GSoC team for their continued support.
+I'm pleased to announce that Mozilla has been accepted as a mentoring organization in the 2020 Google Summer Of Code, and would like to express our gratitude to everyone on the GSoC team for their continued support.
 
-This is the first year that we've organized Mozilla's application to GSoC on Github. Mozilla community members, please put your ideas in the */proposals/* directory, in some suitably-titled file, so that we can evaluate them and polish them up.
+This is the first year that we've organized Mozilla's application to GSoC on Github. Mozilla community members, please put your ideas in the /proposals/ directory, in some suitably-titled file, so that we can evaluate them and polish them up.
 
 ## For Mozillians and friends of Mozilla:
 
-As usual this will be an opportunity to coach a smart student through three months of work on an interesting but non-critical-path project that is open to any part of Mozilla, provided: 
+As usual, this will be an opportunity to coach a smart student through three months of work on an interesting but non-critical-path project that is open to any part of Mozilla, provided:
 
 * the project is primarily a coding project, 
 * the proposal is well-scoped with clearly defined progress milestones and outcomes, taking roughly 3 months of effort for a capable student, and 
 * there is a mentor specifically assigned to the project who is available for the duration of GSoC.
 
-You may already have a student in mind for a specific project already; if so, please start that discussion now. The sooner we have well-specified project ideas lined up with potential mentors, the better. 
+You may already have a student in mind for a specific project already; if so, please start that discussion now. The sooner we have well-specified project ideas lined up with potential mentors, the better.
 
-Otherwise please send us your proposals (via pull request) and feel free to bring us any questions you have about GSoC and Mozilla's participation in it. If Mozilla is accepted as a participating organization the student application period will begin March 16th. 
+Otherwise please send us your proposals (via pull request) and feel free to bring us any questions you have about GSoC and Mozilla's participation in it. If Mozilla is accepted as a participating organization the student application period will begin March 16th.
 
-With all that in mind, we're now accepting project proposals,via pull request to the */proposals/* directory of this repo.
+With all that in mind, we're now accepting project proposals, via pull request to the /proposals/ directory of this repo.
 
 ## Are you a student intending to apply to participate in GSoC with Mozilla? 
 
-Your first stop should be to look over the /proposals/ folder. Not all of those ideas will make the cut; it could be that they are not properly defined, the wrong size, or don't have a mentor, and that makes them less likely to get accepted. We may simply be awarded fewer GSoC slots than we have projects. 
+Your first stop should be to look over the /proposals/ folder. Not all of those ideas will make the cut; it could be that they are not properly defined, the wrong size, or don't have a mentor, and that makes them less likely to get accepted. We may simply be awarded fewer GSoC slots then we have projects.
 
-We see a lot of questions about what tasks or bugs students can be assigned in the leadup to GSoC, and while we're grateful for the enthuiasm we would like to discourage pepole from taking that approach. While it would be helpful for us to be able to assess applicants' skills ahead of time and we always want to be open to new contributors' help, we don't want to treat our GSOC projects as a prizes you might win if you volunteer hard enough. Asking people to labor performatively is unfair and exploitative, and that is not how we intend to operate or who we want to be. 
+We see a lot of questions about what tasks or bugs students can be assigned in the leadup to GSoC, and while we're grateful for the enthusiasm we would like to discourage people from taking that approach. While it would be helpful for us to be able to assess applicants' skills ahead of time and we always want to be open to new contributors' help, we don't want to treat our GSOC projects as a prize you might win if you volunteer hard enough. Asking people to labor performatively is unfair and exploitative, and that is not how we intend to operate or who we want to be.
 
-With that in mind, while we encourage anyone who is interested to take a look at our code, download and build it - please do, that's why it's there! - we believe that your best approach as a GSoC applicant is to use what you learn there to help you *craft an excellent GSOC proposal*, rather than trying to rack up "points" in order to be considered.
+With that in mind, while we encourage anyone who is interested to take a look at our code, download and build it - please do, that's why it's there! - we believe that your best approach as a GSoC applicant is to use what you learn there to help you craft an excellent GSOC proposal, rather than trying to rack up "points" in order to be considered.
 
 ## Are you a student with a great idea for a GSOC project?