doc/rgw: clarify path-style vs virtual-hosted-style access

instead of referring to "vhost-style", copy the "path-style" and
"virtual-hosted-style" language from https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html

expand the FQDN acronym to avoid potential confusion

"The second method is deprecated by AWS" had incorrectly referred to the
vhost-style method - clarify that it refers to path-style access

Signed-off-by: Casey Bodley <cbodley@redhat.com>

diff --git a/doc/radosgw/s3/commons.rst b/doc/radosgw/s3/commons.rst
index 91cf2e02005fb09d4793564533f7ec454b4b894c..5047f8fdecc1f6a9c461c3ad91dcce5781eaa73a 100644 (file)
--- a/doc/radosgw/s3/commons.rst
+++ b/doc/radosgw/s3/commons.rst
@@ -7,19 +7,19 @@
 
 Bucket and Host Name
 --------------------
-There are two different modes of accessing buckets. The first method identifies
-the bucket as the top-level directory in the URI::
+There are two different modes of accessing buckets: path-style and virtual-hosted-style.
+Path-style requests identify the bucket as the top-level directory of the request's path::
 
        GET /mybucket HTTP/1.1
        Host: cname.domain.com
 
-Most S3 clients nowadays rely on vhost-style access. The desired bucket is
-indicated by a DNS FQDN. For example::
+Most S3 clients default to virtual-hosted-style access, where the bucket name is instead
+indicated as part of the fully-qualified domain name::
 
        GET / HTTP/1.1
        Host: mybucket.cname.domain.com
 
-The second method is deprecated by AWS. See the `Amazon S3 Path Deprecation
+Path-style access is deprecated by AWS. See the `Amazon S3 Path Deprecation
 Plan`_ for more information.
 
 To configure virtual hosted buckets, you can either set ``rgw_dns_name =