Indexing and storage: Implement suggestions by CodeRabbit

Author: amotl

docs/feature/storage/indexing-and-storage.md

@@ -224,7 +224,7 @@ and y in [9,11], the engine does the following:
 
 ## Doc values
 
-:::{rubric} Data storage prior to Lucene 4.0
+:::{rubric} Data storage before Lucene 4.0
 :::
 
 Until Lucene 4.0, columns were indexed using an inverted index data structure
@@ -251,7 +251,7 @@ store numerics (single- or multivalued), sorted keywords (single or
 multivalued) and binary data blobs per document.
 These values are quite fast to access at search time, since they are
 stored column-stride such that only the value for that one field needs
-to be decoded per hit. This is in contrast to Lucene's stored document
+to be decoded per hit. Compared to Lucene's stored document
 fields, which store all field values for one document together in a
 row-stride fashion, and are therefore relatively slow to access.
 >