Apply suggestions from code review

Co-authored-by: Xi Zhang <[email protected]>

docs/dapp/tools/verification.md

@@ -21,16 +21,14 @@ or deployment script contains `import '@oasisprotocol/sapphire-hardhat'` or
 comment those out for the deployment.
 
 Verification services will try to match the contract deployment transaction code
-with the one in the provided contract's metadata and since the transaction was
+with the one in the provided contract's metadata. Because the transaction was
 encrypted with an ephemeral ParaTime key, the verification service will not be
 able to decrypt it. Some services may extract the contract's bytecode from the
 chain directly by calling `eth_getCode` RPC, but this will not work correctly
 for contracts with immutable variables.
 
 :::
 
-
-
 ## Verification with Hardhat
 
 If you use Hardhat to deploy your contracts, consider using the
@@ -112,7 +110,7 @@ To verify maunally a contract deployed on Sapphire Mainnet or Testnet on Sourcif
 
    ![Sourcify: Verify contract](../images/tools/sourcify3.png)
 
-4. If everything goes well, you will get a *Perfect match* notice and your
+4. If everything goes well, you will get a *Perfect match* notice. your
    contract is now verified. Congratulations!
 
 In case of a *Partial match*, the contracts metadata JSON differs from the one