doc/radosgw: update and clarify layout and placement

Signed-off-by: Anthony D'Atri <anthony.datri@gmail.com>

diff --git a/doc/radosgw/layout.rst b/doc/radosgw/layout.rst
index 6ee0bc2a8ed6c424c728866ae5e95fa57cb31d45..1f105cf08f955ca5fd515736914bf12ab4a5df03 100644 (file)
--- a/doc/radosgw/layout.rst
+++ b/doc/radosgw/layout.rst
@@ -96,7 +96,7 @@ causes no ambiguity. For the same reason, slashes are permitted in object
 names (keys).
 
 It is also possible to create multiple data pools and make it so that
-different users buckets will be created in different RADOS pools by default,
+different users\` buckets will be created in different RADOS pools by default,
 thus providing the necessary scaling. The layout and naming of these pools
 is controlled by a 'policy' setting.[3]
 
@@ -132,16 +132,17 @@ Footnotes
 to how Extended Attributes associate with a POSIX file. An object's omap
 is not physically located in the object's storage, but its precise
 implementation is invisible and immaterial to RADOS Gateway.
-In Hammer, one LevelDB is used to store omap in each OSD.
+In Hammer, LevelDB is used to store omap data within each OSD; later releases
+default to RocksDB but can be configured to use LevelDB.
 
 [2] Before the Dumpling release, the 'bucket.instance' metadata did not
 exist and the 'bucket' metadata contained its information. It is possible
 to encounter such buckets in old installations.
 
-[3] The pool names have been changed starting with the Infernalis release.
+[3] Pool names changed with the Infernalis release.
 If you are looking at an older setup, some details may be different. In
 particular there was a different pool for each of the namespaces that are
-now being used inside the default.root.meta pool.
+now being used inside the ``default.root.meta`` pool.
 
 Appendix: Compendium
 --------------------

diff --git a/doc/radosgw/placement.rst b/doc/radosgw/placement.rst
index 4931cc87d384e60d1acc69e813286a96bdbfc00b..c255cccb3553f31d37942a730fdbeb4a4d4047af 100644 (file)
--- a/doc/radosgw/placement.rst
+++ b/doc/radosgw/placement.rst
@@ -239,8 +239,8 @@ name in an HTTP header with the request. The S3 protocol uses the
 ``X-Amz-Storage-Class`` header, while the Swift protocol uses the
 ``X-Object-Storage-Class`` header.
 
-When using AWS S3 SDKs such as python boto3, it is important that the non-default
-storage class will be called as one on of the AWS S3 allowed storage classes, or else the SDK
+When using AWS S3 SDKs such as ``boto3``, it is important that non-default
+storage class names match those provided by AWS S3, or else the SDK
 will drop the request and raise an exception.
 
 S3 Object Lifecycle Management can then be used to move object data between