btree.3: grfix

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man3/btree.3

@@ -133,7 +133,7 @@ Obviously, using a cache increases (but only increases) the likelihood of
 corruption or lost data if the system crashes while a tree is being modified.
 If
 .I cachesize
-is 0 (no size is specified) a default cache is used.
+is 0 (no size is specified), a default cache is used.
 .TP
 .I maxkeypage
 The maximum number of keys which will be stored on any single page.
@@ -144,7 +144,7 @@ Not currently implemented.
 .\" must always be greater than or equal to 2.
 .\" If
 .\" .I maxkeypage
-.\" is 0 (no maximum number of keys is specified) the page fill factor is
+.\" is 0 (no maximum number of keys is specified), the page fill factor is
 .\" made as large as possible (which is almost invariably what is wanted).
 .TP
 .I minkeypage
@@ -155,14 +155,14 @@ by the minkeypage value, it will be stored on overflow pages instead
 of in the page itself.
 If
 .I minkeypage
-is 0 (no minimum number of keys is specified) a value of 2 is used.
+is 0 (no minimum number of keys is specified), a value of 2 is used.
 .TP
 .I psize
 Page size is the size (in bytes) of the pages used for nodes in the tree.
 The minimum page size is 512 bytes and the maximum page size is 64K.
 If
 .I psize
-is 0 (no page size is specified) a page size is chosen based on the
+is 0 (no page size is specified), a page size is chosen based on the
 underlying filesystem I/O block size.
 .TP
 .I compare
@@ -202,7 +202,7 @@ The number should represent the order as an integer; for example,
 big endian order would be the number 4,321.
 If
 .I lorder
-is 0 (no order is specified) the current host order is used.
+is 0 (no order is specified), the current host order is used.
 .PP
 If the file already exists (and the
 .B O_TRUNC