Cleaned up proposal review and project slot description.

Author: kgodey

content/gsoc-2019/contents.lr

@@ -27,27 +27,22 @@ Here are short bios of each of our 2019 mentors. Please use first names or Slack
 
 ## Proposal review criteria
 
-Proposal quality is very important, code and community contributions help for different reasons. 
-We are hoping that GSoC will lead to long term contributions to CC, and we see being involved in the community as a sign 
-of general interest in our work. Any code contributions are good for first purposes, contributions to CC repos also 
-show a general interest in our work so they count for both.
-
 We do not have formal guidelines for reviewing proposals, but here are a few things we consider:
 * **Quality of the proposal**: This is the most important thing. A good proposal includes attention to detail, externally measurable milestones, consideration for future maintainability and community involvement, and a demonstration of your skills.
-* **Community involvement**: One of our major goals for GSoC is to build an active development community and attract long-term contributors. Engaging in the community, whether it's asking questions, helping other students, contributing code, filing bugs, or whatever else, is a good sign that you're actually interested in our work and our projects.
+* **Community involvement**: One of our major goals for GSoC is to build an active development community and attract long-term contributors. We see engaging in the community, whether it's asking questions, helping other students, contributing code, filing bugs, or whatever else, as a sign that you're genuinely interested in our work.
+* **Code contributions**: We appreciate seeing your code, it helps us gauge your ability to orient yourself to a new codebase, as well as giving us confidence that you have the skills necessary to implement your proposal. Code samples that are not related to CC projects work too, but contributing to CC projects has the added benefits of community involvement.
 * **Communication skills and initiative**: These are essential to completing a successful project. Things we look for (among others): asking specific and detailed questions, following up on conversations, making sure to read available resources before asking questions, being patient and responding to critical feedback well.
-* **Code contributions**: We appreciate seeing your code, it helps us gauge your ability to orient yourself to a new codebase, as well as giving us confidence that you have the skills necessary to implement your proposal. Code samples that are not related to CC projects are fine too.
 
-However, this is all relative. As is said above, we do not have any formal guidelines. 
-If you have a great proposal, but haven't contributed to any CC repos, you still have a good shot.
+However, this is all relative. For example. if you have a great proposal, but haven't contributed code to CC yet, you still have a good shot.
 
-## Project slots
+## Number of accepted students
 
-Google assigns Creative Commons (and all GSoC organizations) a fixed number of project slots. This means that there may be `n` 
-proposals on the project ideas page, but CC may only be allocated enough project slots to support `< n` projects. 
+We can only accept a fixed number of students, which is determined by the number of slots allocated to
+ us by the Google Summer of Code administrators. Even though there are `n` proposals 
+on the project ideas page, CC may only be allocated enough project slots to support fewer than `n` projects. 
 The number of project slots allocated to each GSoC organization varies by year. 
 
-You can find more information about the slot allocation process in [the GSoC mentor guide][GSoC-Slot-Allocation].
+You can find more information about the slot allocation process in [the GSoC mentor guide][gsoc-slot-allocation].
 
 ## History
 
@@ -60,4 +55,4 @@ CC participated in Google Summer of Code seven previous times. See below for mor
 * [Google Summer of Code 2012](https://www.google-melange.com/archive/gsoc/2012/orgs/cc)
 * [Google Summer of Code 2013](https://www.google-melange.com/archive/gsoc/2013/orgs/cc)
 
-[GSoC-Slot-Allocation]: https://google.github.io/gsocguides/mentor/selecting-students-and-mentors#the-formal-process
+[gsoc-slot-allocation]: https://google.github.io/gsocguides/mentor/selecting-students-and-mentors#the-formal-process