gsoc/organisation_application: fix some typos spotted by tschwinge

1 files changed, 7 insertions, 7 deletions

diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn
index 6a6389d8..471f3bdc 100644
--- a/community/gsoc/organization_application.mdwn
+++ b/community/gsoc/organization_application.mdwn
@@ -82,7 +82,7 @@ spreading technical and other knowledge about the Hurd among actual and
 potential contributors.
 
 Last but not least, we hope the participation will have a positive effect on
-our community -- new impulses, increased communication etc.
+our community -- new impulses, increased communication, etc.
 
 * Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
 
@@ -91,7 +91,7 @@ we participated under the umbrella of the GNU project, getting one slot each
 year.
 
 In 2008 we participated as an organisation on our own for the first time. This
-turned out extremely beneficial: With the better visibility, we get a lot
+turned out extremely beneficial: with the better visibility, we got a lot
 more applications (more than 20), mostly of good or excellent quality.
 
 In 2009, we were rejected as an organisation, so we participated under the GNU
@@ -103,7 +103,7 @@ spite of not getting a slot. Half of them are regular Hurd contributors now.
 
 Selecting the most promising students, as well as suitable mentors, turned out
 to be the most tricky part of GSoC participation -- but we learned our lesson
-after the first failure: We didn't have any students that didn't meet our
+after the first failure: we didn't have any students that didn't meet our
 expectations since then, and we also believe our mentoring is exceptionally
 good now -- one project that was in serious trouble, turned out well after all,
 due to effective mentor intervention.
@@ -169,7 +169,7 @@ their work, so that we get partial results at least if someone disappears.
 
 As our mentors all have been with the project for some time, the risk of them
 disappearing is not too big. If one of them disappears nevertheless, it's not a
-problem for us: We have enough mentors, and someone else will take over.
+problem for us: we have enough mentors, and someone else will take over.
 
 We will encourage the students to keep discussions public as much as possible,
 keeping private conversations with the mentors to a minimum, so the transition
@@ -182,14 +182,14 @@ contact with us before the end of the student selection process, and won't
 consider their applications otherwise. This way we know that the students are
 able and willing to communicate with us in the first place.
 
-After selection, the regular contact is kept up: We require the
+After selection, the regular contact is kept up: we require the
 students to participate in IRC meetings up to twice a week, where we ask the students
-actively about the work they do, problems they face, decisions they take etc.
+actively about the work they do, problems they face, decisions they take, etc.
 Furthermore, we ask them to hang out on IRC most of the time while
 working on their projects, so we keep in close contact.
 
 We also require the students to join our main development mailing list, so any
-design questions etc. can be discussed there. We encourage them to take
+design questions, etc. can be discussed there. We encourage them to take
 part in other conversations, not directly related to their projects, as well.
 
 After the program we continue the regular meetings, discussing the further