Index: main/waeup.kofa/trunk/docs/source/userdocs/applicants.rst
===================================================================
--- main/waeup.kofa/trunk/docs/source/userdocs/applicants.rst	(revision 13232)
+++ main/waeup.kofa/trunk/docs/source/userdocs/applicants.rst	(revision 13273)
@@ -34,5 +34,5 @@
   in Python docstrings the term 'application' predominates.
 
-Much like students, applicants are also a users of the portal and
+Much like students, applicants are also users of the portal and
 the applicant object is a user account surrogate, see
 :ref:`Applicants and Students <applicants_and_students>`. In the
@@ -40,5 +40,5 @@
 about an applicant.
 
-In contrast to students containers, applicant containers do not
+In contrast to student containers, applicant containers do not
 contain subcontainers. The only objects they contain are applicant
 payment tickets (i.e. instances of `ApplicantOnlinePayment`). Thus
Index: main/waeup.kofa/trunk/docs/source/userdocs/applicants/create_students.rst
===================================================================
--- main/waeup.kofa/trunk/docs/source/userdocs/applicants/create_students.rst	(revision 13232)
+++ main/waeup.kofa/trunk/docs/source/userdocs/applicants/create_students.rst	(revision 13273)
@@ -12,5 +12,5 @@
 1. Officers can create student records from single applicant
    records. A link button appears on the display page of each admitted
-   applicants which directly triggers the creation process:
+   applicant which directly triggers the creation process:
 
   |create_student_button|
@@ -23,8 +23,8 @@
 
   Only admitted applicants will be processed. Other selected
-  applicants will be skipped without further notice
+  applicants will be skipped without further notice.
 
 3. Last but not least, the portal manager with user id ``admin``
-   does see a link buttons:
+   does see a link button:
 
   |create_students_button|
