fix: wording of integrator options (#1059)

src/pages/dev/amplifier/chain-integration/integrate-a-chain.mdx

@@ -203,7 +203,7 @@ Use the existing deployments for all three contracts, making note of the existin
 </tab-item>
 
 <tab-item title="Use custom implementation">
-You can also deploy a custom implementation of the gateway, verifier, and prover contracts and optimize them with the [`Cosmwasm rust-optimizer`](https://github.com/CosmWasm/optimizer). Follow the same steps as Option 2 with your own implementations of the Amplifier contracts.
+You can also deploy a custom implementation of the gateway, verifier, and prover contracts and optimize them with the [`Cosmwasm rust-optimizer`](https://github.com/CosmWasm/optimizer). Follow the same steps as you would with your own implementations of the Amplifier contracts.
 </tab-item>
 
 </tabs>
@@ -365,4 +365,4 @@ Every new chain will need a verifier, which requires running `ampd` and `tofnd`.
 
 ## Begin routing messages
 
-Once your chain is registered with the protocol, it will need verifiers to begin routing messages. See [Become an Amplifier Verifier (Worker)](/validator/amplifier/verifier-onboarding) for instructions to onboard a verifier. Note that chain integrators will onboard on `devnet-amplifier` and not `devnet-verifier`.
+Once your chain is registered with the protocol, it will need verifiers to begin routing messages. See [Become an Amplifier Verifier (Worker)](/validator/amplifier/verifier-onboarding) for instructions to onboard a verifier. Note that chain integrators will onboard on `devnet-amplifier` and not `devnet-verifier`.