From 26b99b1fecf653302b9dc3802604d871a9c2f347 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jos=C3=A9=20Pedro=20Sousa?= Date: Tue, 8 Oct 2024 15:56:09 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Savio <72797635+Savio-Sou@users.noreply.github.com> --- docs/docs/getting_started.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/getting_started.md b/docs/docs/getting_started.md index 6e3d996b1cf..e8b88823ddc 100644 --- a/docs/docs/getting_started.md +++ b/docs/docs/getting_started.md @@ -71,7 +71,7 @@ y = "2" We're now ready to compile and execute our Noir program. By default the `nargo execute` command will do both, and generate the `witness` that we need to feed to our proving backend: ```sh -nargo execute hello-witness +nargo execute ``` You can now see the witness and the compiled circuit in the `target` folder. We're ready to prove @@ -81,7 +81,7 @@ You can now see the witness and the compiled circuit in the `target` folder. We' Using the `bb` CLI tool as an example: ```sh -bb prove -b ./target/hello_world.json -w ./target/hello-witness.gz -o ./target/proof +bb prove -b ./target/hello_world.json -w ./target/hello-world.gz -o ./target/proof ``` :::tip