doc/radosgw: s/s3select/S3 Select/

Correct several misspelling of "S3 Select". Hat tip to Anthony D'Atri,
who caught this in an earlier PR.

Signed-off-by: Zac Dover <zac.dover@proton.me>

diff --git a/doc/radosgw/s3select.rst b/doc/radosgw/s3select.rst
index 0c1046a3883c5691f07dd6ebc273643b394f0d67..d46d4e96f2e19078d4f7a606069de3bfb0a26b63 100644 (file)
--- a/doc/radosgw/s3select.rst
+++ b/doc/radosgw/s3select.rst
@@ -7,14 +7,14 @@
 Overview
 --------
 
-The **s3 select** engine creates an efficient pipe between clients and Ceph
+The **S3 Select** engine creates an efficient pipe between clients and Ceph
 back end nodes. The S3 Select engine works best when implemented as closely as
 possible to back end storage.
 
 The S3 Select engine makes it possible to use an SQL-like syntax to select a
-restricted subset of data stored in an S3 object. The s3select engine
+restricted subset of data stored in an S3 object. The S3 Select engine
 facilitates the use of higher level, analytic applications (for example:
-SPARK-SQL). The ability of the s3select engine to target a proper subset of
+SPARK-SQL). The ability of the S3 Select engine to target a proper subset of
 structed data within an S3 object decreases latency and increases throughput.
 
 For example: assume that a user needs to extract a single column that is
@@ -22,7 +22,7 @@ filtered by another column, and that these colums are stored in a CSV file in
 an S3 object that is several GB in size. The following query performs this
 extraction: ``select customer-id from s3Object where age>30 and age<65;``
 
-Without the use of s3select, the whole S3 object must be retrieved from an OSD
+Without the use of S3 Select, the whole S3 object must be retrieved from an OSD
 via RGW before the data is filtered and extracted. Significant network and CPU
 overhead are saved by "pushing down" the query into radosgw.