diff --git a/doc/radosgw/STS.rst b/doc/radosgw/STS.rst
index 12a5f5eb849..bc89b89da60 100644
--- a/doc/radosgw/STS.rst
+++ b/doc/radosgw/STS.rst
@@ -110,8 +110,8 @@ Examples
 
    radosgw-admin caps add --uid="TESTER" --caps="roles=*"
 
-2. The following is an example of AssumeRole API call, which shows steps to create a role, assign a policy to it
-   (that allows access to S3 resources), assuming a role to get temporary credentials and accessing s3 resources using
+2. The following is an example of the AssumeRole API call, which shows steps to create a role, assign a policy to it
+   (that allows access to S3 resources), assuming a role to get temporary credentials and accessing S3 resources using
    those credentials. In this example, TESTER1 assumes a role created by TESTER, to access S3 resources owned by TESTER,
    according to the permission policy attached to the role.
 
diff --git a/doc/radosgw/STSLite.rst b/doc/radosgw/STSLite.rst
index 7145d0d2379..7880e373f46 100644
--- a/doc/radosgw/STSLite.rst
+++ b/doc/radosgw/STSLite.rst
@@ -35,7 +35,7 @@ Parameters:
     **TokenCode** (String/ Optional): The value provided by the MFA device, if MFA is required.
 
 An administrative user needs to attach a policy to allow invocation of GetSessionToken API using its permanent
-credentials and to allow subsequent s3 operations invocation using only the temporary credentials returned
+credentials and to allow subsequent S3 operations invocation using only the temporary credentials returned
 by GetSessionToken.
 
 The user attaching the policy needs to have admin caps. For example::