Fix typos in auth doc

Co-authored-by: Nate Prewitt <[email protected]>

Author: JordonPhillips

designs/auth.md

@@ -105,12 +105,12 @@ class Identity(Protocol):
 ```
 
 An `Identity` may be derived from any number of sources, such as configuration
-properties or environement variables. These different sources are loaded by an
+properties or environment variables. These different sources are loaded by an
 [`IdentityResolver`](#identity-resolvers).
 
 ### Identity Resolvers
 
-Identity resolvers are responsible for contructiong an `Identity` for a request.
+Identity resolvers are responsible for constructing an `Identity` for a request.
 
 ```python
 class IdentityResolver[I: Identity, IP: Mapping[str, Any]](Protocol):
@@ -120,14 +120,14 @@ class IdentityResolver[I: Identity, IP: Mapping[str, Any]](Protocol):
 ```
 
 Each identity source SHOULD have its own identity resolver implementation. If an
-`Identity` is supported by multiple `IdentityResolver`s, those resolver SHOULD
+`Identity` is supported by multiple `IdentityResolver`s, those resolvers SHOULD
 be prioritized to provide a stable resolution strategy. A
 `ChainedIdentityResolver` implementation is provided that implements this
 behavior generically.
 
 The `get_identity` function takes only one (keyword-only) argument - a mapping
 of properties that is refined by the `IP` generic parameter. The identity
-properties are contructed by the `AuthScheme`'s `identity_properties` method.
+properties are constructed by the `AuthScheme`'s `identity_properties` method.
 
 Identity resolvers are constructed by the `AuthScheme`'s `identity_resolver`
 method.
@@ -153,7 +153,7 @@ request.
 
 ### Event Signers
 
-Auh schemes MAY also have an associated event signer, which signs events that
+Auth schemes MAY also have an associated event signer, which signs events that
 are sent to a server. They behave in the same way as normal signers, except that
 they sign an event instead of a transport request. The properties passed to this
 signing method are identical to those pased to the request signer.
@@ -168,7 +168,7 @@ class EventSigner[I, SP: Mapping[str, Any]](Protocol):
 
 ## Configuration
 
-All services with at least one auth trait will have the following properites on
+All services with at least one auth trait will have the following properties on
 their configuration object.
 
 ```python

packages/smithy-core/src/smithy_core/aio/interfaces/auth.py

@@ -24,7 +24,7 @@ async def sign(self, *, request: R, identity: I, properties: SP) -> R:
 
 
 class EventSigner[I, SP: Mapping[str, Any]](Protocol):
-    """A class that signs requests before they are sent."""
+    """A class that signs events before they are sent."""
 
     # TODO: add a protocol type for events
     async def sign(self, *, event: Any, identity: I, properties: SP) -> Any:

packages/smithy-core/src/smithy_core/auth.py

@@ -34,10 +34,10 @@ class AuthOption:
     """The ID of the auth scheme to use."""
 
     identity_properties: _TypedProperties = field(default_factory=TypedProperties)
-    """Paramters to pass to the identity resolver method."""
+    """Parameters to pass to the identity resolver method."""
 
     signer_properties: _TypedProperties = field(default_factory=TypedProperties)
-    """Paramters to pass to the signing method."""
+    """Parameters to pass to the signing method."""
 
 
 class DefaultAuthResolver:

packages/smithy-core/src/smithy_core/interfaces/auth.py

@@ -17,10 +17,10 @@ class AuthOption(Protocol):
     """The ID of the auth scheme to use."""
 
     identity_properties: TypedProperties
-    """Paramters to pass to the identity resolver method."""
+    """Parameters to pass to the identity resolver method."""
 
     signer_properties: TypedProperties
-    """Paramters to pass to the signing method."""
+    """Parameters to pass to the signing method."""
 
 
 class AuthSchemeResolver(Protocol):