Update builders/pallets-precompiles/precompiles/relay-data-verifier.md

builders/pallets-precompiles/precompiles/relay-data-verifier.md

@@ -97,7 +97,7 @@ A typical workflow to verify relay chain data involves the following steps:
 
 3. **Relay RPC Call** - call the `state_getReadProof(keys, at)` RPC method to retrieve the storage proof, where `at` is the relay block hash obtained in step 2, `keys` is an Array of strings which contains the keys for target storage items. For `@polkadot/api`, it can be obtained via `api.query.module.key()` function
 
-4. **Moonbeam RPC Call** - Submit an Ethereum transaction to call the `verifyEntry` or `verifyEntries` function to verify the data against the relay block number. The call data should contain the relay block number obtained in Step 1, the read proof generated in Step 3, and the key(s) to verify
+4. **Moonbeam RPC Call** - submit an Ethereum transaction to call the `verifyEntry` or `verifyEntries` function to verify the data against the relay block number. The call data should contain the relay block number obtained in Step 1, the read proof generated in Step 3, and the key(s) to verify
 
 The following sections will cover how to interact with the Identity Precompile using Ethereum libraries, such as Ethers.js, Web3.js, and Web3.py. The examples in this guide will be on Moonbase Alpha.