Update design docs

design/client/identity_and_auth.html

@@ -214,7 +214,7 @@ <h3 id="the-configuration-stage"><a class="header" href="#the-configuration-stag
 <li><strong>IdentityResolver:</strong> resolves an identity for use in authentication.
 There can be multiple identity resolvers that need to be selected from.</li>
 <li><strong>Signer:</strong> a signing implementation that signs a HTTP request.</li>
-<li><strong>AuthSchemeOptionResolver:</strong> resolves a list of auth scheme options for a given operation and its inputs.</li>
+<li><strong>ResolveAuthSchemeOptions:</strong> resolves a list of auth scheme options for a given operation and its inputs.</li>
 </ul>
 </li>
 </ul>
@@ -230,7 +230,7 @@ <h3 id="the-execution-stage"><a class="header" href="#the-execution-stage">The e
 <ol>
 <li>Retrieve the <code>AuthSchemeOptionResolverParams</code> from the config bag. The <code>AuthSchemeOptionResolverParams</code> allow client
 config and operation inputs to play a role in which auth scheme option is selected.</li>
-<li>Retrieve the <code>AuthSchemeOptionResolver</code> from the config bag, and use it to resolve the auth scheme options available
+<li>Retrieve the <code>ResolveAuthSchemeOptions</code> impl from the config bag, and use it to resolve the auth scheme options available
 with the <code>AuthSchemeOptionResolverParams</code>. The returned auth scheme options are in priority order.</li>
 <li>Retrieve the <code>IdentityResolvers</code> list from the config bag.</li>
 <li>For each auth scheme option:
@@ -260,7 +260,7 @@ <h2 id="how-this-looks-in-rust"><a class="header" href="#how-this-looks-in-rust"
     scheme_id: &amp;'static str,
 }
 
-pub trait AuthSchemeOptionResolver: Send + Sync + Debug {
+pub trait ResolveAuthSchemeOptions: Send + Sync + Debug {
     fn resolve_auth_scheme_options&lt;'a&gt;(
         &amp;'a self,
         params: &amp;AuthSchemeOptionResolverParams,

design/print.html

@@ -1091,7 +1091,7 @@ <h3 id="the-configuration-stage"><a class="header" href="#the-configuration-stag
 <li><strong>IdentityResolver:</strong> resolves an identity for use in authentication.
 There can be multiple identity resolvers that need to be selected from.</li>
 <li><strong>Signer:</strong> a signing implementation that signs a HTTP request.</li>
-<li><strong>AuthSchemeOptionResolver:</strong> resolves a list of auth scheme options for a given operation and its inputs.</li>
+<li><strong>ResolveAuthSchemeOptions:</strong> resolves a list of auth scheme options for a given operation and its inputs.</li>
 </ul>
 </li>
 </ul>
@@ -1107,7 +1107,7 @@ <h3 id="the-execution-stage"><a class="header" href="#the-execution-stage">The e
 <ol>
 <li>Retrieve the <code>AuthSchemeOptionResolverParams</code> from the config bag. The <code>AuthSchemeOptionResolverParams</code> allow client
 config and operation inputs to play a role in which auth scheme option is selected.</li>
-<li>Retrieve the <code>AuthSchemeOptionResolver</code> from the config bag, and use it to resolve the auth scheme options available
+<li>Retrieve the <code>ResolveAuthSchemeOptions</code> impl from the config bag, and use it to resolve the auth scheme options available
 with the <code>AuthSchemeOptionResolverParams</code>. The returned auth scheme options are in priority order.</li>
 <li>Retrieve the <code>IdentityResolvers</code> list from the config bag.</li>
 <li>For each auth scheme option:
@@ -1137,7 +1137,7 @@ <h2 id="how-this-looks-in-rust"><a class="header" href="#how-this-looks-in-rust"
     scheme_id: &amp;'static str,
 }
 
-pub trait AuthSchemeOptionResolver: Send + Sync + Debug {
+pub trait ResolveAuthSchemeOptions: Send + Sync + Debug {
     fn resolve_auth_scheme_options&lt;'a&gt;(
         &amp;'a self,
         params: &amp;AuthSchemeOptionResolverParams,