wording

Rewritten-docs.md

@@ -190,7 +190,7 @@ and achieved score (amount of awarded points).
 
 ## Requirements
 
-There are bunch of different formal requirements for the system. Some of them
+There are many different formal requirements for the system. Some of them
 are necessary for any system for source code evaluation, some of them are
 specific for university deployment and some of them arose during the ten year
 long lifetime of the old system. There are not many ways to improve CodEx
@@ -208,18 +208,17 @@ System features represents directly accessible functionality to users of the
 system.  They describe the evaluation system in general and also university
 addons (mostly administrative features).
 
-#### Pure user requirements
+#### End user requirements
 
-- users have their own account in the system
+- users have their own accounts in the system
 - system users can be members of multiple groups (reflecting courses or labs)
 - there is a database of exercises; teachers can create exercises including
   textual description, sample inputs and correct reference outputs (for example
-  "sum all numbers from given file and write the result to the standard
-  output")
-- there is a list of assigned exercises in each group and interface to submit a
-  solution; teachers can assign an existing exercise to their class with some
+  "sum all numbers from given file and write the result to the standard output")
+- there is a list of assigned exercises in each group and an interface to submit
+  a solution; teachers can assign an existing exercise to their class with some
   specific properties set (deadlines, etc.)
-- user can see a list of submitted solutions for each assignment with
+- users can see a list of submitted solutions for each assignment with
   corresponding results
 - teachers can specify way of computation grading points which will be awarded
   to the students depending on the quality of his/her solution for each