Add Transaction Control to isolation level

+ some copy-editing

Author: mrotteveel

src/docs/asciidoc/de/refdocs/fblangref40/_fblangref40-dochist-de.adoc

@@ -10,6 +10,11 @@ Die exakte Dateihistorie ist im _Git_-Repository des `firebird-documentation`-Re
 |===
 4+|Historie
 
+|1.8-de
+|29. Juli 2022
+|MR
+|`READ CONSISTENCY` zum <<#fblangref40-transacs-settransac-iso>> hinzugefügt
+
 |1.7-de
 |18. Juli 2022
 |MR

src/docs/asciidoc/de/refdocs/fblangref40/_fblangref40-transacs-de.adoc

@@ -231,7 +231,7 @@ Die drei von Firebird unterstützten Isolationsstufen sind:
 
 * `SNAPSHOT`
 * `SNAPSHOT TABLE STABILITY`
-* `READ COMMITTED` mit zwei Angaben (`NO RECORD_VERSION` und `RECORD_VERSION`)
+* `READ COMMITTED` mit drei Angaben (`READ CONSISTENCY`, `NO RECORD_VERSION` und `RECORD_VERSION`)
 
 [[fblangref40-transacs-settransac-snapshot-de]]
 ====== `SNAPSHOT`-Isolationsstufe

src/docs/asciidoc/de/refdocs/fblangref40/firebird-40-sprachreferenz-de.adoc

@@ -1,7 +1,7 @@
 [[fblangref40-de]]
 = Firebird 4.0 Sprachreferenz
 Dmitry Filippov; Alexander Karpeykin; Alexey Kovyazin; Dmitry Kuzmenko; Denis Simonov; Paul Vinkenoog; Dmitry Yemanov; Mark Rotteveel; Martin Köditz
-1.7-de, 18. Juli 2022
+1.8-de, 29. Juli 2022
 :doctype: book
 :sectnums:
 :sectanchors:

src/docs/asciidoc/en/refdocs/fblangref40/_fblangref40-dochist.adoc

@@ -10,13 +10,19 @@ The exact file history is recorded in our _git_ repository; see https://github.c
 |===
 4+|Revision History
 
+|1.8-de
+|29 Jul 2022
+|MR
+a|* `READ CONSISTENCY` zum <<#fblangref40-transacs-settransac-iso>> hinzugefügt
+* Various copy-editing in _Transaction Control_ chapter
+
 |1.7
-|18 July 2022
+|18 Jul 2022
 |MR
 |Fix documentation for `RDB$INDICES.RDB$INDEX_TYPE` (https://github.com/FirebirdSQL/firebird-documentation/issues/174[#174])
 
 |1.6
-|13 July 2022
+|13 Jul 2022
 |MR
 |`DATEDIFF` unit `MILLISECOND` returns `NUMERIC(18,1)` since Firebird 4.0.1 (https://github.com/FirebirdSQL/firebird-documentation/issues/173[#173])
 

src/docs/asciidoc/en/refdocs/fblangref40/_fblangref40-transacs.adoc

@@ -111,15 +111,15 @@ Available only in ESQL
 
 The `SET TRANSACTION` statement configures the transaction and starts it.
 As a rule, only client applications start transactions.
-The exceptions are the occasions when the server starts an autonomous transaction or transactions for certain background system threads/processes, such as sweeping.
+Exceptions are when the server starts an autonomous transaction, and transactions for certain background system threads/processes, such as sweeping.
 
 A client application can start any number of concurrently running transactions.
 A single connection can have multiple concurrent active transactions (though not all drivers or access components support this).
 A limit does exist, for the total number of running transactions in all client applications working with one particular database from the moment the database was restored from its backup copy or from the moment the database was created originally.
 The limit is 2^48^ -- 281,474,976,710,656 -- in Firebird 3.0 and higher, and 2^31^-1 -- or 2,147,483,647 -- in earlier versions.
 
 All clauses in the `SET TRANSACTION` statement are optional.
-If the statement starting a transaction has no clauses specified in it, it the transaction will be started with default values for access mode, lock resolution mode and isolation level, which are:
+If the statement starting a transaction has no clauses specified, the transaction will be started with default values for access mode, lock resolution mode and isolation level, which are:
 
 [source]
 ----
@@ -131,7 +131,7 @@ SET TRANSACTION
 
 [WARNING]
 ====
-Database drivers or access components may use different defaults.
+Database drivers or access components may use different defaults for transactions started through their API.
 Check their documentation for details.
 ====
 
@@ -155,7 +155,7 @@ The optional `NAME` attribute defines the name of a transaction.
 Use of this attribute is available only in Embedded SQL.
 In ESQL applications, named transactions make it possible to have several transactions active simultaneously in one application.
 If named transactions are used, a host-language variable with the same name must be declared and initialized for each named transaction.
-This is a limitation that prevents dynamic specification of transaction names and thus, rules out transaction naming in DSQL.
+This is a limitation that prevents dynamic specification of transaction names and thus rules out transaction naming in DSQL.
 
 [[fblangref40-transacs-settransac-params]]
 ==== Transaction Parameters
@@ -231,7 +231,7 @@ The three isolation levels supported in Firebird are:
 
 * `SNAPSHOT`
 * `SNAPSHOT TABLE STABILITY`
-* `READ COMMITTED` with two specifications (`NO RECORD_VERSION` and `RECORD_VERSION`)
+* `READ COMMITTED` with three specifications (`READ CONSISTENCY`, `NO RECORD_VERSION` and `RECORD_VERSION`)
 
 [[fblangref40-transacs-settransac-snapshot]]
 ====== `SNAPSHOT` Isolation Level

src/docs/asciidoc/en/refdocs/fblangref40/firebird-40-language-reference.adoc

@@ -1,7 +1,7 @@
 [[fblangref40]]
 = Firebird 4.0 Language Reference
 Dmitry Filippov; Alexander Karpeykin; Alexey Kovyazin; Dmitry Kuzmenko; Denis Simonov; Paul Vinkenoog; Dmitry Yemanov; Mark Rotteveel
-1.7, 18 July 2022
+1.8, 29 July 2022
 :doctype: book
 :sectnums:
 :sectanchors: