From 16ff08b79443cb1a9963e77530b307156d904d8b Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Thu, 13 Mar 2014 15:01:45 +0200 Subject: [PATCH] Fix a couple of typos in docs. Thom Brown --- doc/src/sgml/gin.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/gin.sgml b/doc/src/sgml/gin.sgml index 0bd759220f..80fb4f3634 100644 --- a/doc/src/sgml/gin.sgml +++ b/doc/src/sgml/gin.sgml @@ -197,7 +197,7 @@ function, and a ternary triConsistent function. triConsistent covers the functionality of both, so providing triConsistent alone is sufficient. However, if the boolean variant is - significantly cheaper to calculate, it can be advantegous to provide both. + significantly cheaper to calculate, it can be advantageous to provide both. If only the boolean variant is provided, some optimizations that depend on refuting index items before fetching all the keys are disabled. @@ -219,7 +219,7 @@ returned by extractQuery for this query datum. Each element of the check array is TRUE if the indexed item contains the - corresponding query key, ie, if (check[i] == TRUE) the i-th key of the + corresponding query key, i.e., if (check[i] == TRUE) the i-th key of the extractQuery result array is present in the indexed item. The original query datum is passed in case the consistent method needs to consult it, -- 2.40.0