typoes

Author: bumblefudge

CAIPs/caip-104.md

@@ -170,7 +170,7 @@ this reference depends on.
 
 Namespace-CAIPs may also have a `superseded-by` header indicating that an CAIP
 has been rendered obsolete by a later document; the value is the `title` that
-replaces the current document, i.e., if "eip155-caip10" gets superceded, it
+replaces the current document, i.e., if "eip155-caip10" gets superseded, it
 should rename in the directory `eip155` directory but contain a link to the
 superseding specification(s), like `[caip10v2](caip10v2.md)`. The newer
 Namespace-CAIP must have a `replaces` header containing the number of the

CAIPs/caip-122.md

@@ -19,7 +19,7 @@ When accompanied with chain-specific message forms and signing algorithms, along
 ## Motivation
 
 As specified in [EIP-4361][], Sign in With Ethereum defined an Ethereum-focused workflow to authenticate Ethereum accounts on non-blockchain services. 
-This work is meant to generalize and abstract the Sign in With Ethereum specification, thereby making EIP-4361 a specific implementation of this specification, to work with any cryptographic system's namespace expressable in [CAIP-10][] and [CAIP-2][] formats.
+This work is meant to generalize and abstract the Sign in With Ethereum specification, thereby making EIP-4361 a specific implementation of this specification, to work with any cryptographic system's namespace expressible in [CAIP-10][] and [CAIP-2][] formats.
 
 Additionally, [CAIP-74][] specified a way to represent a chain-agnostic capability object (OCAP) by placing an EIP-4361 message into a CACAO container.
 

CAIPs/caip-169.md

@@ -184,7 +184,7 @@ occur.
 
 Called **by the wallet** to the application, providing the parameters needed for
 a credential issuance and expecting back a verifiable credential OR an error.
-The parameters are formated as a [credential_application object][] as specified
+The parameters are formatted as a [credential_application object][] as specified
 in the [Credential Manifest][] specification.
 
 #### Method: