fmt

Author: mysteryon88

contract-dev/zero-knowledge.mdx

@@ -107,6 +107,7 @@ Output example:
 The **trusted setup** is a one-time ceremony that generates the proving and verification keys for a circuit. It's called "trusted" because if the setup parameters are compromised, proofs could be forged. For production use, participate in a multi-party trusted setup ceremony. For local development and testing, a simplified single-party setup is sufficient. For local tests, perform a simplified trusted setup ceremony.
 
 The "power of tau" parameter (`10`) has to be chosen
+
 - as low as possible, because it affects execution time;
 - high enough, because the more constraints in the scheme, the higher the parameter required.
 
@@ -317,4 +318,4 @@ This guide demonstrates a minimal example: **circuit → trusted setup → verif
 - Noname: [`zksecurity/noname`](https://github.com/zksecurity/noname)
 - `gnark`: [`consensys/gnark`](https://github.com/Consensys/gnark)
 - Arkworks: [`arkworks`](https://arkworks.rs/)
-- SnarkJS: [`iden3/snarkjs`](https://github.com/iden3/snarkjs)
+- SnarkJS: [`iden3/snarkjs`](https://github.com/iden3/snarkjs)