diff --git a/mkdocs/docs/circom-language/signals.md b/mkdocs/docs/circom-language/signals.md
index 23255e6..7278271 100644
--- a/mkdocs/docs/circom-language/signals.md
+++ b/mkdocs/docs/circom-language/signals.md
@@ -28,7 +28,7 @@ component main {public [in1,in2]} = Multiplier2();
 
 This example declares input signals `in1` and `in2` of the main component as public signals.
 
-In circom, all output signals of the main component are public (and cannot be made private), the input signals of the main component are private if not stated otherwise using the keyword public as avobe. The rest of signals are all private and cannot be made public. 
+In circom, all output signals of the main component are public (and cannot be made private), the input signals of the main component are private if not stated otherwise using the keyword public as above. The rest of signals are all private and cannot be made public. 
 
 Thus, from the programmer's point of view, only public input and output signals are visible from outside the circuit, and hence no intermediate signal can be accessed.
 
diff --git a/mkdocs/docs/getting-started/proving-circuits.md b/mkdocs/docs/getting-started/proving-circuits.md
index 4eefde4..215ba15 100644
--- a/mkdocs/docs/getting-started/proving-circuits.md
+++ b/mkdocs/docs/getting-started/proving-circuits.md
@@ -119,7 +119,7 @@ Export the verification key:
 snarkjs zkey export verificationkey multiplier2_0001.zkey verification_key.json
 ```
 
-### Generating a Groph16 ZKP <a id="my-first-zero-knowledge-proof"></a>
+### Generating a Groth16 ZKP <a id="my-first-zero-knowledge-proof"></a>
 
 Once the witness is computed and the trusted setup is already executed, we can **generate a zk-proof** associated to the circuit and the witness: