diff --git a/GSoC-2015-Organization-Application.rest b/GSoC-2015-Organization-Application.rest
index 7ca4d8c..0182038 100644
--- a/GSoC-2015-Organization-Application.rest
+++ b/GSoC-2015-Organization-Application.rest
@@ -38,7 +38,7 @@ What is your plan for dealing with disappearing mentors?
   Our mentors are core members of the community, including Andreas Rumpf, the author of the Nim programming language himself. I highly doubt that any mentor would disappear since we don't take this responsibility lightly, but another mentor could jump in.
 
 What steps will you take to encourage students to interact with your project's community before and during the program?
-  On our ideas page we're asking them to join our IRC channel and discuss potential ideas with us. It's very important for us to get in touch with students before, to make sure to find a fitting project for each student, and make them understand and help with their independent research.
+  On our ideas page we're asking them to join our IRC channel and discuss potential ideas with us. It's very important for us to get in touch with students before, to make sure to find a fitting project for each student, and make them understand and help with their independent research. During the program we also expect the students to continuously interact with us via IRC.
 
 What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes?
   We will propose ideas of further improving their GSoC work and other potential projects with Nim.