diff --git a/extension/Documentation/Manual.rst b/extension/Documentation/Manual.rst
index 7b0f91b13000f9bdb7ef061a8c29aabe8ac6034a..612bfa06495f8060f4f3ff1e56d1ec223c95d1da 100644
--- a/extension/Documentation/Manual.rst
+++ b/extension/Documentation/Manual.rst
@@ -530,7 +530,7 @@ Fill STORE_SYSTEM by SQL
 A specified SELECT statement in `configuration`_ in variable `fillStoreSystemBySql1` (or `2`,
 or `3`) will be fired. The query should have 0 (nothing happens) or 1 row. All columns will be
 **added** to the existing STORE_SYSTEM. Existing variables will be overwritten. Be careful not to overwrite system values.
- 
+
 This option is useful to make generic custom values, saved in the database, accessible to all QFQ Report and Forms.
 Access such variables via `{{<varname>:Y}}`.
 
@@ -2037,14 +2037,14 @@ After the user presses *Save*, *Close*, *Delete* or *New*, different actions are
 
 * `auto` (default) - the QFQ browser Javascript logic, decides to stay on the page or to force a redirection
   to a previous page. The decision depends on:
-  
+
   * *Close* goes back (feels like close) to the previous page. Note: if there is no history, QFQ won't close the tab,
      instead a message is shown.
   * *Save* stays on the current page.
 
 * `close` - goes back (feels like close) to the previous page. Note: if there is no history, QFQ won't close the tab,
      instead a message is shown.
-* `no` - no change, the browser remains on the current side. Close does not close the page. It just triggers a save if 
+* `no` - no change, the browser remains on the current side. Close does not close the page. It just triggers a save if
   there are modified data.
 * `url` - the browser redirects to the URL or T3 page named in `Forward URL / Page`. Independent if the user presses `save` or `close`.
 * `url-skip-history` - same as `url`, but the current location won't saved in the browser history.
@@ -5229,7 +5229,7 @@ Render mode
 
 The following table might be hard to read - but it's really useful to understand. It solves a lot of different situations.
 If there are no special condition (like missing value, or suppressed links), render mode 0 is sufficient.
-But if the URL text is missing, or the URL is missing, OR the link should be rendered in sql row 1-10, but not 5, than
+But if the URL text is missing, or the URL is missing, OR the link should be rendered in sql row 1-10, but not 5, then
 render mode might dynamically control the rendered link.
 
 * Column *Mode* is the render mode and controls how the link is rendered.
@@ -5239,7 +5239,7 @@ render mode might dynamically control the rendered link.
 +============+=====================+====================+==================+=======================================================================+
 |0 (default) |<a href=url>text</a> |<a href=url>url</a> |                  |text or image will be shown, only if there is a url, page or mailto    |
 +------------+---------------------+--------------------+------------------+-----------------------------------------------------------------------+
-|1           |<a href=url>text</a> |<a href=url>url</a> |text              |Text or image will be shown, independet of there is a url              |
+|1           |<a href=url>text</a> |<a href=url>url</a> |text              |Text or image will be shown, independent of there is a url              |
 +------------+---------------------+--------------------+------------------+-----------------------------------------------------------------------+
 |2           |<a href=url>text</a> |                    |                  |no link if text is empty                                               |
 +------------+---------------------+--------------------+------------------+-----------------------------------------------------------------------+
@@ -7182,5 +7182,3 @@ Open the 'Webdeveloper Tools' (FF: F12, Chrome/Opera: Right mouse click > Inspec
 
 
 .. _`webserverErrorLog`:
-
-