@@ -216,8 +216,8 @@ GIN indexes
216216JsQuery extension contains two operator classes (opclasses) for GIN which
217217provide different kinds of query optimization.
218218
219- * jsonb\_ value\_ path\_ ops
220219* jsonb\_ path\_ value\_ ops
220+ * jsonb\_ value\_ path\_ ops
221221
222222In each of two GIN opclasses jsonb documents are decomposed into entries. Each
223223entry is associated with particular value and it's path. Difference between
@@ -243,9 +243,9 @@ key "a" is presented three times. In the large branchy documents with long
243243keys size of naive entries representation becomes unreasonable. Both opclasses
244244address this issue but in a slightly different way.
245245
246- ###jsonb\_ value \ _\_ ops
246+ ###jsonb\_ path\_ value \_ ops
247247
248- jsonb\_ value \ _\_ ops represents entry as pair of path hash and value.
248+ jsonb\_ path\_ value \_ ops represents entry as pair of path hash and value.
249249Following pseudocode illustrates it.
250250
251251(hash(path_item_1.path_item_2. ... .path_item_n); value)
@@ -256,9 +256,9 @@ is hashed and it is higher part of entry we need to know the full path to
256256the value in order to use it for search. However, once path is specified
257257we can use both exact and range searches very efficiently.
258258
259- ###jsonb\_ path \ _\_ ops
259+ ###jsonb\_ value\_ path \_ ops
260260
261- jsonb\_ path \ _\_ ops represents entry as pair of value and bloom filter
261+ jsonb\_ value\_ path \_ ops represents entry as pair of value and bloom filter
262262of path.
263263
264264(value; bloom(path_item_1) | bloom(path_item_2) | ... | bloom(path_item_n))