Apply suggestions from code review

Co-authored-by: Jordon Phillips <JordonPhillips@users.noreply.github.com>

Author: lucix-aws

docs/source-2.0/guides/client-guidance/identity-auth/index.md

@@ -73,7 +73,7 @@ identification would sign an outgoing HTTP request by presenting the value of
 the token in the `Authorization` header.
 
 All signers require, at a minimum, a request to sign and an identity with which
-to sign. A Signer should be modeled like so:
+to sign. A `Signer` should be modeled like so:
 
 ```java
 // This example interface modifies the transport message in-place with the
@@ -87,7 +87,7 @@ public interface Signer<TIdentity extends Identity, TMessage extends Message> {
 
 ## AuthScheme
 
-An AuthScheme self-describes a single flow (combination of an identity resolver
+An `AuthScheme` self-describes a single flow (combination of an identity resolver
 and signer) through which a Smithy client authenticates a request:
 
 ```java
@@ -119,9 +119,9 @@ public interface IdentityResolverConfig {
 }
 ```
 
-A list of supported AuthSchemes should be configurable by the end-user of the
+A list of supported `AuthScheme`s should be configurable by the end-user of the
 Smithy client. The default "constructor" for a Smithy client should typically
-pre-load a list of supported AuthSchemes on client configuration.
+pre-load a list of supported `AuthScheme`s on client configuration.
 
 ```java
 // in this example, the service supports some combination of