A couple of rewordings and format changes before tech review

Signed-off-by: Fanit Kolchina <[email protected]>

Author: kolchfa-aws

_field-types/supported-field-types/knn-vector.md

@@ -268,6 +268,7 @@ return Byte(bval)
 {% include copy.html %}
 
 ## Faiss byte vector
+
 Faiss engine is recommended for use cases that requires ingestion on a large scale. But, for these large scale workloads using the default `float` vectors requires a lot of memory usage as each dimension is 4 bytes. If you want to reduce this memory and storage requirements,
 you can use `byte` vectors with the `faiss` engine. In a `byte` vector, each dimension is a signed 8-bit integer in the [-128, 127] range.
 

_search-plugins/knn/knn-vector-quantization.md

@@ -14,7 +14,8 @@ By default, the k-NN plugin supports the indexing and querying of vectors of typ
 OpenSearch supports many varieties of quantization. In general, the level of quantization will provide a trade-off between the accuracy of the nearest neighbor search and the size of the memory footprint consumed by the vector search. The supported types include byte vectors, 16-bit scalar quantization, and product quantization (PQ).
 
 ## Faiss byte vector
-Starting with version 2.17, the k-NN plugin supports `byte` vectors with the Faiss engine which helps to reduce the memory requirements. For more information, see [Faiss byte vector]({{site.url}}{{site.baseurl}}/field-types/supported-field-types/knn-vector#faiss-byte-vector).
+
+Starting with version 2.17, the k-NN plugin supports `byte` vectors with the Faiss engine in order to reduce the amount of required memory. For more information, see [Faiss byte vector]({{site.url}}{{site.baseurl}}/field-types/supported-field-types/knn-vector#faiss-byte-vector).
 
 ## Lucene byte vector