Few typos in cap-0046-11.md (#1392)

Co-authored-by: Dmytro Kozhevin <dmytro@stellar.org>

core/cap-0046-11.md

@@ -110,7 +110,7 @@ module.
 authorization data, performs authentication, provides replay protection, and
 enforces the authorization context.
 
-In the following sections each of the components is descirbed in detail.
+In the following sections each of the components is described in detail.
 
 ### Authorization Payload in Transaction
 
@@ -271,7 +271,7 @@ as specified in transaction.
 
 `create_contract` host function pushes a special stack frame identifying that
 'create contract' host function is running and implicitly calls a special
- implementaiton of `require_auth(deployer)` with the arguments being 
+ implementation of `require_auth(deployer)` with the arguments being 
 `CreateContractArgs` inferred from the `create_contract` arguments. The same
 procedure is also applied to the `InvokeHostFunctionOp` operations with
 `HOST_FUNCTION_TYPE_CREATE_CONTRACT` host function variant.
@@ -497,7 +497,7 @@ speicifcation and writes it to the ledger.
 
 Due to the signature expiration verification procedure the nonce entry is
 guaranteed to stay in the ledger until the signature expires. After the nonce
-entyr (and thus the signature) expire, nonce value can be reused for in the new
+entry (and thus the signature) expires, nonce value can be reused for in the new
 `SorobanAddressCredentials` entry for the account with a new expiration ledger.
 
 ##### Important Propeties of the Algorithm