diff --git a/docs/src/guides/advanced/91_docker_and_ci.md b/docs/src/guides/advanced/91_docker_and_ci.md index 885d3155dd6c..77a8d2cc212a 100644 --- a/docs/src/guides/advanced/91_docker_and_ci.md +++ b/docs/src/guides/advanced/91_docker_and_ci.md @@ -4,7 +4,7 @@ How to efficiently debug CI issues locally. This document will be useful in case you struggle with reproducing some CI issues on your local machine. -In most cases, this is due to the fact that your local machine has some arifacts, configs, files that you might have set +In most cases, this is due to the fact that your local machine has some artifacts, configs, files that you might have set in the past, that are missing from the CI. ## Basic docker commands diff --git a/docs/src/specs/interop/interopmessages.md b/docs/src/specs/interop/interopmessages.md index f32724e0013d..572dfcea37d6 100644 --- a/docs/src/specs/interop/interopmessages.md +++ b/docs/src/specs/interop/interopmessages.md @@ -79,7 +79,7 @@ only if someone has first called `signup_open()` on chain A. ```solidity // Contract deployed on chain A. contract SignupManager { - public bytes32 sigup_open_msg_hash; + public bytes32 signup_open_msg_hash; function signup_open() onlyOwner { // We are open for business signup_open_msg_hash = InteropCenter(INTEROP_CENTER_ADDRESS).sendInteropMessage("We are open"); diff --git a/docs/src/specs/prover/circuit_testing.md b/docs/src/specs/prover/circuit_testing.md index 159d908642ff..2671ebe8f7f8 100644 --- a/docs/src/specs/prover/circuit_testing.md +++ b/docs/src/specs/prover/circuit_testing.md @@ -38,7 +38,7 @@ Now the constraint system is ready! We can start the main part of the test! ![Contest(8).png](<./img/circuit_testing/Contest(8).png>) Here we have hard coded a secret key with its associated public key, and generate a signature. We will test our circuit -on these inputs! Next we “allocate” these inputs as witnessess: +on these inputs! Next we “allocate” these inputs as witnesses: ![Contest(9).png](<./img/circuit_testing/Contest(9).png>)