typo operate_bridge.md

kadena/docs/src/run/operate_bridge.md

@@ -105,7 +105,7 @@ for different use cases.
 > The following documentation will be for SNARK proofs, as they are the only
 > proofs that can be verified on our home chains.
 
-The core data to be passed to any verification contrtact are the following:
+The core data to be passed to any verification contract are the following:
 - Verifying key: A unique key represented as 32 bytes, related to the program that is meant to be verified
 - Public values: Serialized public values of the proof
 - Proof: The serialized proof to be verified
@@ -149,4 +149,4 @@ verification. The logic that has to be kept for the inclusion verification
 and the committee change program are showcased in our Solidity contracts ([longest chain](https://github.com/argumentcomputer/zk-light-clients/blob/dev/kadena/solidity/contracts/src/Wrapper.sol#L105) and [spv](https://github.com/argumentcomputer/zk-light-clients/blob/dev/kadena/solidity/contracts/src/Wrapper.sol#L117-L129)).
 
 The place where a user can add its own use case logic is where we currently print out some values
-for both the [longest chain](https://github.com/argumentcomputer/zk-light-clients/blob/dev/kadena/solidity/contracts/src/Wrapper.sol#L107) and [spv](https://github.com/argumentcomputer/zk-light-clients/blob/dev/kadena/solidity/contracts/src/Wrapper.sol#L131)).
+for both the [longest chain](https://github.com/argumentcomputer/zk-light-clients/blob/dev/kadena/solidity/contracts/src/Wrapper.sol#L107) and [spv](https://github.com/argumentcomputer/zk-light-clients/blob/dev/kadena/solidity/contracts/src/Wrapper.sol#L131)).