Update README.md

README.md

@@ -22,13 +22,13 @@ With all that in mind, we're now accepting project proposals,via pull request to
 
 Your first step 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. 
 
-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 enthuiasm we would like to discourage people from taking that approach. While it would be helpful for us to be able to assess applicant's skills ahead of time and we always want to be open to new contributor's 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. 
 
 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?
 
-You can, of course, also submit your own ideas; a great idea doesn't need to come from Mozilla to be a great GSoC project.  For us to accept a proposal as a GSoC project, your proposal *must have* a mentor, a defined outcome of reasonable scope, and a calendar with meaningful milestones to have a shot at acceptance. You can submit your proposals either as pull requests to this repo, or as applications through the GSoC process itself. Bear in mind that projects that come as a surprise to the proposed mentor are unlikely to be accepted, so you should have had a conversation with the Mozillians whose support you'd like well ahead of time.
+You can, of course, also submit your own ideas; a great idea doesn't need to come from Mozilla to be a great GSoC project. For us to accept a proposal as a GSoC project, your proposal *must have* a mentor, a defined outcome of reasonable scope, and a calendar with meaningful milestones to have a shot at acceptance. You can submit your proposals either as pull requests to this repo, or as applications through the GSoC process itself. Bear in mind that projects that come as a surprise to the proposed mentor are unlikely to be accepted, so you should have had a conversation with the Mozillians whose support you'd like well ahead of time.
 
 That said, there are a lot of moving parts to the Mozilla project, and figuring out who to talk to can be difficult even if you've got an amazing idea. If this is you, please start by *opening an issue describing your idea* so we can take a look at it. While we can't promise anything, if your idea looks promising we will do our best to connect you to somebody with domain-relevant experience to discuss turning it into a proposal.