Misc copy-editing

Author: mrotteveel

src/docs/asciidoc/en/refdocs/fblangref60/_langref-commons.adoc

@@ -120,14 +120,14 @@ Formally, the syntax of a normal string literal is:
 ----
 
 * In Dialect 3, double quotes are _not valid_ for quoting strings.
-The SQL standard reserves double quotes for a different purpose: delimiting or quoting identifiers.
+The SQL standard reserves double quotes for a different purpose: delimiting or quoting <<langref-structure-identifiers,identifiers>>.
 * If a literal apostrophe is required within a string constant, it is "`escaped`" by prefixing it with another apostrophe.
 For example, `++'Mother O''Reilly''s home-made hooch'++`.
-Or use the alternative quote literal: `++q'{Mother O'Reilly's home-made hooch}'++`
+Or use the <<langref-commons-qstrings,alternative quote literal>>: `++q'{Mother O'Reilly's home-made hooch}'++`
 * Care should be taken with the string length if the value is to be written to a `CHAR` or `VARCHAR` column.
 The maximum length for a `CHAR` or `VARCHAR` literal is 32,765 bytes.
 
-The character set of a string constant is assumed to be the same as the character set of its destined storage.
+The character set of a string literal is assumed to be the same as the character set of its destined storage.
 
 .Examples
 [source]
@@ -286,9 +286,7 @@ For backwards compatibility, some values of 19 digits are mapped to `NUMERIC(18,
 ===== Hexadecimal Notation for Numbers
 
 Integer values can also be entered in hexadecimal notation.
-Numbers with 1-8 hex digits will be interpreted as type `INTEGER`;
-numbers with 9-16 hex digits as type `BIGINT`;
-numbers with 17-32 hex digits as type `INT128`.
+Numbers with 1-8 hex digits will be interpreted as type `INTEGER`, 9-16 hex digits as type `BIGINT`, and 17-32 hex digits as type `INT128`.
 
 .Syntax
 [listing,subs=+quotes]
@@ -314,28 +312,28 @@ select 0xFFFFFFFFFFFFFFFF from rdb$database  -- returns -1
 [#langref-commons-hexranges]
 ====== Hexadecimal Value Ranges
 
-* Hex numbers in the range 0 ... 7FFF FFFF are positive ``INTEGER``s with values between 0 ... 2147483647 decimal.
+* Hex numbers in the range `0` ... `7FFF FFFF` are positive ``INTEGER``s with values between `0` ... `2147483647` decimal.
 To coerce a number to `BIGINT`, prepend enough zeroes to bring the total number of hex digits to nine or above.
 That changes the type but not the value.
-* Hex numbers between 8000 0000 ... FFFF FFFF require some attention:
+* Hex numbers between `8000 0000` ... `FFFF FFFF` and `8000 0000 0000 0000` ... `FFFF FFFF FFFF FFFF` require some attention:
 +
 --
 ** When written with eight hex digits, as in `0x9E44F9A8`, a value is interpreted as 32-bit `INTEGER`.
-Since the leftmost bit (sign bit) is set, it maps to the negative range -2147483648 ... -1 decimal.
-** With one or more zeroes prepended, as in `0x09E44F9A8`, a value is interpreted as 64-bit `BIGINT` in the range 0000 0000 8000 0000 ... 0000 0000 FFFF FFFF.
-The sign bit is not set now, so they map to the positive range 2147483648 ... 4294967295 decimal.
+Since the leftmost bit (sign bit) is set, it maps to the negative range `-2147483648` ... `-1` decimal.
+** With one or more zeroes prepended, as in `0x09E44F9A8`, a value is interpreted as 64-bit `BIGINT` in the range `0000 0000 8000 0000` ... `0000 0000 FFFF FFFF`.
+The sign bit is not set now, so they map to the positive range `2147483648` ... `4294967295` decimal.
 --
 +
-Thus, in this range, and for 16 vs 16+ digits, prepending a mathematically insignificant 0 results in a different value.
+Thus, for 8 vs 8+ digits, and for 16 vs 16+ digits, prepending a mathematically insignificant 0 results in a different value.
 This is something to be aware of. 
-* Hex numbers between 0 0000 0001 ... 7FFF FFFF FFFF FFFF are all positive `BIGINT`.
-* Hex numbers between 8000 0000 0000 0000 ... FFFF FFFF FFFF FFFF are all negative `BIGINT`.
-* Hex numbers between 0 0000 0000 0000 0001 ... 7FFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF are all positive `INT128`
-* Hex numbers between 8000 0000 0000 0000 0000 0000 0000 0000 ... FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF are all negative `INT128`
+* Hex numbers between `0 0000 0001` ... `7FFF FFFF FFFF FFFF` are all positive `BIGINT`.
+* Hex numbers between `8000 0000 0000 0000` ... `FFFF FFFF FFFF FFFF` are all negative `BIGINT`.
+* Hex numbers between `0 0000 0000 0000 0001` ... `7FFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF` are all positive `INT128`
+* Hex numbers between `8000 0000 0000 0000 0000 0000 0000 0000` ... `FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF` are all negative `INT128`
 * A `SMALLINT` cannot be written in hex, strictly speaking, since even `0x0` and `0x1` are evaluated as `INTEGER`.
-However, if you write a positive integer within the 16-bit range `0x0000` (decimal zero) to `0x7FFF` (decimal 32767) it will be converted to `SMALLINT` transparently.
+However, if you write a positive integer within the 16-bit range `0x0000` (decimal `0`) to `0x7FFF` (decimal `32767`) it will be converted to `SMALLINT` transparently.
 + 
-It is possible to write to a negative `SMALLINT` in hex, using a 4-byte hex number within the range `0xFFFF8000` (decimal -32768) to `0xFFFFFFFF` (decimal -1).
+It is possible to write to a negative `SMALLINT` in hex, using a 4-byte hex number within the range `0xFFFF8000` (decimal `-32768`) to `0xFFFFFFFF` (decimal `-1`).
 
 [#langref-commons-boolean-literal]
 ==== Boolean Literals
@@ -549,38 +547,38 @@ FROM EMPLOYEE
 
 [#langref-dtyp-tbl-arithpreced]
 .Arithmetic Operator Precedence
-[cols="<1,<2,<1", options="header",stripes="none"]
+[cols="<1m,<2,<1", options="header",stripes="none"]
 |===
 ^| Operator
 ^| Purpose
 ^| Precedence
 
-|`{plus}signed_number`
+|{plus}signed_number
 |Unary plus
 |1
 
-|`-signed_number`
+|-signed_number
 |Unary minus
 |1
 
-|`{asterisk}`
+|{asterisk}
 |Multiplication
 |2
 
-|`/`
+|/
 |Division
 |2
 
-|`{plus}`
+|{plus}
 |Addition
 |3
 
-|`-`
+|-
 |Subtraction
 |3
 |===
 
-Where operators have the same precedence, they are evaluated in left-to-right sequence.
+Where operators have the same precedence, they are evaluated in left-to-right order.
 
 .Example
 [source]
@@ -594,45 +592,45 @@ UPDATE T
 
 [#langref-dtyp-tbl-comparpreced]
 .Comparison Operator Precedence
-[cols="<1,<2,<1", options="header",stripes="none"]
+[cols="<1m,<2,<1", options="header",stripes="none"]
 |===
 ^| Operator
 ^| Purpose
 ^| Precedence
 
-|`IS`
+|IS
 |Checks that the expression on the left is (not) `NULL` or the Boolean value on the right
 |1
 
-|`=`
+|=
 |Is equal to, is identical to
 |2
 
-|`<>`, `!=`, `~=`, `^=`
+|<>, !=, ~=, ^=
 |Is not equal to
 |2
 
-|`>`
+|>
 |Is greater than
 |2
 
-|`<`
+|<
 |Is less than
 |2
 
-|`>=`
+|>=
 |Is greater than or equal to
 |2
 
-|`++<=++`
+|++<=++
 |Is less than or equal to
 |2
 
-|`!>`, `~>`, `^>`
+|!>, ~>, ^>
 |Is not greater than
 |2
 
-|`!<`, `~<`, `^<`
+|!<, ~<, ^<
 |Is not less than
 |2
 |===
@@ -654,21 +652,21 @@ IF (SALARY > 1400) THEN
 
 [#langref-dtyp-tbl-logical]
 .Logical Operator Precedence
-[cols="<1,<2,<1", options="header",stripes="none"]
+[cols="<1m,<2,<1", options="header",stripes="none"]
 |===
 ^| Operator
 ^| Purpose
 ^| Precedence
 
-|`NOT`
+|NOT
 |Negation of a search condition
 |1
 
-|`AND`
+|AND
 |Combines two or more predicates, each of which must be true for the entire predicate to be true
 |2
 
-|`OR`
+|OR
 |Combines two or more predicates, of which at least one predicate must be true for the entire predicate to be true
 |3
 |===
@@ -750,8 +748,8 @@ All other conditional expressions apply internal functions derived from `CASE` a
 The `CASE` construct returns a single value from a number of possible values.
 Two syntactic variants are supported: 
 
-* The _simple_{nbsp}``CASE``, comparable to a _case construct_ in Pascal or a _switch_ in C
-* The _searched_{nbsp}``CASE``, which works like a series of "```if ... else if ... else if```"{nbsp}clauses.
+* The <<langref-commons-conditional-case-simple,_simple_ ``CASE``>>, comparable to a _case construct_ in Pascal or a _switch_ in C
+* The <<langref-commons-conditional-case-srched,_searched_ ``CASE``>>, which works like a series of "```if ... else if ... else if```" clauses.
 
 [#langref-commons-conditional-case-simple]
 ===== Simple `CASE`
@@ -927,7 +925,7 @@ WHERE EXISTS
      AND O.adate = DATE '10.03.1990');
 ----
 
-When subqueries are used to get the values of the output column in the `SELECT` list, a subquery must return a _scalar_ result (see below).
+When subqueries are used to get the values of the output column in the `SELECT` list, a subquery must return a <<langref-commons-scalarsq,_scalar_ result>>.
 
 [#langref-commons-scalarsq]
 ==== Scalar Results

src/docs/asciidoc/en/refdocs/fblangref60/_langref-dochist.adoc

@@ -16,7 +16,7 @@ The exact file history is recorded in our _git_ repository; see https://github.c
 a|* Copied the _Firebird 5.0 Language Reference_ as a starting point:
 ** Renamed files and reference using _fblangref50_ to _langref_ (new naming convention)
 ** Where applicable, replaced references to Firebird 5.0 with Firebird 6.0
-* ...
+* Documented `SCHEMA` DDL
 
 |===