Fix incorrect articles and misplaced backtick in NatSpec comments

contracts/token/ERC20/extensions/ERC1363.sol

@@ -33,7 +33,7 @@ abstract contract ERC1363 is ERC20, ERC165, IERC1363 {
     error ERC1363TransferFromFailed(address sender, address receiver, uint256 value);
 
     /**
-     * @dev Indicates a failure within the {approve} part of a approveAndCall operation.
+     * @dev Indicates a failure within the {approve} part of an approveAndCall operation.
      * @param spender Address which will spend the funds.
      * @param value Amount of tokens to be spent.
      */

contracts/utils/TransientSlot.sol

@@ -80,7 +80,7 @@ library TransientSlot {
     }
 
     /**
-     * @dev UDVT that represents a slot holding a int256.
+     * @dev UDVT that represents a slot holding an int256.
      */
     type Int256Slot is bytes32;
 

contracts/utils/cryptography/signers/draft-ERC7739.sol

@@ -16,7 +16,7 @@ import {MessageHashUtils} from "../MessageHashUtils.sol";
  * EIP-712 domains (e.g. a single offchain owner of multiple contracts).
  *
  * This contract requires implementing the {_rawSignatureValidation} function, which passes the wrapped message hash,
- * which may be either an typed data or a personal sign nested type.
+ * which may be either a typed data or a personal sign nested type.
  *
  * NOTE: xref:api:utils/cryptography#EIP712[EIP-712] uses xref:api:utils/cryptography#ShortStrings[ShortStrings] to
  * optimize gas costs for short strings (up to 31 characters). Consider that strings longer than that will use storage,

contracts/utils/draft-InteroperableAddress.sol

@@ -66,8 +66,8 @@ library InteroperableAddress {
     }
 
     /**
-     * @dev Parse a ERC-7930 interoperable address (version 1) into its different components. Reverts if the input is
-     * not following a version 1 of ERC-7930.
+     * @dev Parse an ERC-7930 interoperable address (version 1) into its different components. Reverts if the input is
+     * not following a version 1 of ERC-7930
      *
      * NOTE: Trailing bytes after a valid v1 encoding are ignored. The same decoded address may therefore correspond
      * to multiple distinct input byte strings.