format

Rewritten-docs.md

@@ -1658,20 +1658,21 @@ for implementation of a website.
 
 There are two basic ways how to create a website these days:
 
-- **server-side approach** - the actions of the user are processed on the server and the
+- **server-side approach** - the actions of the user are processed on the server
-  HTML code with the results of the action is generated on the server and sent
+  and the HTML code with the results of the action is generated on the server
-  back to the web browser of the user. The client does not handle any logic
+  and sent back to the web browser of the user. The client does not handle any
-  (apart from rendering of the user interface and some basic user interaction)
+  logic (apart from rendering of the user interface and some basic user
-  and is therefore very simple. The server can use the API server for processing
+  interaction) and is therefore very simple. The server can use the API server
-  of the actions so the business logic of the server can be very simple as well.
+  for processing of the actions so the business logic of the server can be very
-  A disadvantage of this approach is that a lot of redundant data is transferred
+  simple as well.  A disadvantage of this approach is that a lot of redundant
-  across the requests although some parts of the content can be cached (e.g.,
+  data is transferred across the requests although some parts of the content can
-  CSS files). This results in longer loading times of the website.
+  be cached (e.g., CSS files). This results in longer loading times of the
+  website.
 - **server-side rendering with asynchronous updates (AJAX)** - a slightly
   different approach is to render the page on the server as in the previous case
-  but then execute the actions of the user asynchronously using the `XMLHttpRequest`
+  but then execute the actions of the user asynchronously using the
-  JavaScript functionality. Which creates a HTTP request and transfers only the
+  `XMLHttpRequest` JavaScript functionality. Which creates a HTTP request and
-  part of the website which will be updated.
+  transfers only the part of the website which will be updated.
 - **client-side approach** - the opposite approach is to transfer the
   communication with the API server and the rendering of the HTML completely
   from the server directly to the client. The client runs the code (usually
@@ -1938,13 +1939,13 @@ clicking on "See group's page" link following with "Join group" link.
  in hierarchy and membership cannot be established by students themselves.
  Management of students in this type of groups is in the hands of supervisors.
 
-On the group detail page there are multiple interesting things for you. The first
+On the group detail page there are multiple interesting things for you. The
-one is a brief overview containing the information describing the group, there is a list of
+first one is a brief overview containing the information describing the group,
-supervisors and also the hierarchy of the subgroups. The most important section
+there is a list of supervisors and also the hierarchy of the subgroups. The most
-is the "Student's dashboard" section. This section contains the list of assignments and
+important section is the "Student's dashboard" section. This section contains
-the list of fellow students. If the supervisors of the group allowed students to see the
+the list of assignments and the list of fellow students. If the supervisors of
-statistic of their fellow students then there will also be the number of
+the group allowed students to see the statistic of their fellow students then
-points each of the students has gained so far.
+there will also be the number of points each of the students has gained so far.
 
 ### Start Solving Assignments