From 7be0ce63a4195bf05098159092b73a4ece1052d6 Mon Sep 17 00:00:00 2001
From: Elias Villiger <elias.villiger@uzh.ch>
Date: Thu, 2 Feb 2017 15:56:51 +0100
Subject: [PATCH] Einige Umformulierungen und Tippfehler im User Manual.

---
 extension/Documentation/UsersManual/Index.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/extension/Documentation/UsersManual/Index.rst b/extension/Documentation/UsersManual/Index.rst
index 7b9f910c4..5595ee3aa 100644
--- a/extension/Documentation/UsersManual/Index.rst
+++ b/extension/Documentation/UsersManual/Index.rst
@@ -624,7 +624,7 @@ extraDeleteForm
 '''''''''''''''
 
 Depending on the database definition, it might be necessary to delete the primary record *and* corresponding slave records.
-To not repeat such 'slave record delete definition', an 'extraDeleteForm' could be specified. If the user open's a record
+To not repeat such 'slave record delete definition', an 'extraDeleteForm' can be specified. If the user opens a record
 in a form and clicks on the 'delete' button, a defined 'extraDeleteForm'-form will be used to delete primary and slave
 records instead of using the current form.
 E.g. if there are multiple different forms to work on the same table, all of theses forms might reference to the same
@@ -1069,7 +1069,7 @@ will be rendered inside the form as a HTML table.
   * *form*: Target form, e.g. *form=person*
   * *page*: Target page with detail form. If none specified, use the current page.
   * *title*: Title displayed over the table in the current form.
-  * *extraDeleteForm*: Optional. The per row delete Button will reference such form (for deleting) instead of *form* (default).
+  * *extraDeleteForm*: Optional. The per row delete Button will reference the form specified here (for deleting) instead of the default (*form*).
   * *detail*: Mapping of values from the primary form to the target form (defined via `form=...`).
 
     * Syntax::
@@ -1202,7 +1202,7 @@ sqlInsert / sqlUpdate / sqlDelete
 '''''''''''''''''''''''''''''''''
 
   * Save values of a form to different record(s), optionally on different table(s).
-  * Typically usefull on 'afterSave' - be carefull when using it earlier, e.g. beforeLoad.
+  * Typically useful on 'afterSave' - be careful when using it earlier, e.g. beforeLoad.
 
 FormElement.’‘’parameter’‘’:
 
@@ -1442,8 +1442,8 @@ Text across several lines
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
 To make SQL queries, or QFQ records in general, more readable, it's possible to split a line across several lines. Lines
-with keywords are on their own (`QFQ Keywords (Bodytext)`_) starts a new line - if a line is not a 'keyword' line, it will
-be appended at the last keyword line. 'Keyword' lines are detected on:
+with keywords are on their own (`QFQ Keywords (Bodytext)`_ start a new line). If a line is not a 'keyword' line, it will
+be appended to the last keyword line. 'Keyword' lines are detected on:
 
  * <level>.<keyword> =
  * {
@@ -1501,7 +1501,7 @@ last character of that line must be one of '{}[]()<>'. The corresponding braces
 
 Per QFQ tt-content record, only one type of nesting braces can be used.
 
-Be carefull to:
+Be careful to:
 
 * write nothing else than whitespaces/newline behind an **open brace**
 * the **closing brace** has to be alone on a line. ::
@@ -2727,7 +2727,7 @@ records not exist, the form should create it.
 
 Form primary table: Person
 
-Form salve table: Address
+Form slave table: Address
 
 Relation: `Person.id = Address.personId`
 
@@ -2769,7 +2769,7 @@ Form: Person Wizard - firstname, single note
 --------------------------------------------
 
 Requirement: A form that displays the column 'firstname' from table 'Person' and 'note' from table 'Note'.
-If the records not exist, the form should create it.
+If the records don't exist, the form should create it.
 Column Person.noteId points to Note.id
 
 Form primary table: Person
-- 
GitLab