Introduction

Here's some more changes. These are all small, I'm saving the larger document for later.

pages/optoverview.in:

This one turned up in some changes from last time:

Index: pages/optoverview.in
==================================================================
--- pages/optoverview.in
+++ pages/optoverview.in
@@ -1010,6 +1010,6 @@
   and the outer query (which is likely a join) will be forced to either
   do a full table scan on the transient table or else construct a
-  [query-time index] on the transient table, neither or which is
-  is particularly fast.
+  [query-time index] on the transient table, neither of which is
+  particularly fast.
 
 <p>

pages/lang_corefunc.in:

Index: pages/lang_corefunc.in
==================================================================
--- pages/lang_corefunc.in
+++ pages/lang_corefunc.in
@@ -16,5 +16,5 @@
   that cannot be converted to a numeric value.)^  ^If X is the
   integer -9223372036854775808 then abs(X) throws an integer overflow
-  error since there is no equivalent positive 64-bit two complement value.
+  error since there is no equivalent positive 64-bit two's complement value.
 }
 
@@ -95,5 +95,5 @@
   <p>The iif() function originally required exactly three arguments.
   The two-argument version of iif() and the ability to spell the function as "if()"
-  where features added in SQLite version 3.48.0 ([dateof:3.48.0])
+  were features added in SQLite version 3.48.0 ([dateof:3.48.0])
   The ability to accept more than 3 arguments was added in
   SQLite version 3.49.0 ([dateof:3.49.0]).
@@ -105,5 +105,5 @@
   Y is nowhere found within X.
   ^Or, if X and Y are both BLOBs, then instr(X,Y) returns one
-  more than the number bytes prior to the first occurrence of Y, or 0 if
+  more than the number of bytes prior to the first occurrence of Y, or 0 if
   Y does not occur anywhere within X.
   ^If both arguments X and Y to instr(X,Y) are non-NULL and are not BLOBs

pages/cintro.in

Here's another change:

Index: pages/cintro.in
==================================================================
--- pages/cintro.in
+++ pages/cintro.in
@@ -98,5 +98,5 @@
 <p>
   The [database connection] and [prepared statement] objects are controlled
-  by a small set of C/C++ interface routine listed below.
+  by a small set of C/C++ interface routines listed below.
 </p>
 

pages/pgszchng2016.in

This one's been around a while:

Index: pages/pgszchng2016.in
==================================================================
--- pages/pgszchng2016.in
+++ pages/pgszchng2016.in
@@ -10,5 +10,5 @@
 An SQLite database file consists of one or more "pages".
 For a single database file, all pages are the same size, though
-for different database files, the page size can any power of
+for different database files, the page size can be any power of
 two between 512 and 65536, inclusive.
 </p>

That should be all for now.

Until later, RTDoc brickviking
(Post 0o100)