Update docs/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx

Co-authored-by: Molly Karcher <molly@stellar.org>

Author: karthikiyer56

docs/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx

@@ -87,7 +87,7 @@ Every token transfer event includes comprehensive metadata to provide context ab
 | `ledgerSequence` | `uint32` | The ledger number where this event occurred. This provides chronological ordering across the entire network. |
 | `txHash` | `string` | The transaction hash that generated this event. This allows you to trace events back to their originating transaction. |
 | `operationIndex` | `uint32*` | The one-based index of the operation within the transaction that caused this event as defined by [SEP-35][sep35]. This field is `nil` for transaction-level events like fees. |
-| `contractAddress` | `string` | The contract address asociated with the asset/token being moved. For classic operations or Stellar Asset Contract Events, this field will be the contractId of the underlying classic asset. This enables integration with Stellar's smart contract ecosystem. |
+| `contractAddress` | `string` | The contract address associated with the asset/token being moved. For classic operations or Stellar Asset Contract Events, this field will be the contractId of the underlying classic asset. This enables integration with Stellar's smart contract ecosystem. |
 
 :::note