Website Summary Files Commits Branches @commit @diff @stats
diff options
context:
space:
mode:
Commit3d8e1531df94c94683985096ca40c2b806da1f8d (patch)
Author
 Kamen Mladenov <kamen@syndamia.com>
2025-02-13 09:33:58 +0200
Committer
 Kamen Mladenov <kamen@syndamia.com>
2025-02-13 12:58:08 +0200
Files972560f0fb76fb218f67f02b8dead3eace9537eb
zkVMs-benchmarks-3d8e1531df94c94683985096ca40c2b806da1f8d.tar
zkVMs-benchmarks-3d8e1531df94c94683985096ca40c2b806da1f8d.tar.gz
zkVMs-benchmarks-3d8e1531df94c94683985096ca40c2b806da1f8d.zip
Parent32311fc5d09daf4e946cd0d5add04273bc0a78b2 (diff)
fix(zkvms/README): Squash typos
1 files changed, 1 insertions, 1 deletions
-rw-r--r--zkvms/README.md2
diff --git a/zkvms/README.md b/zkvms/README.md
index 7a2c93a..2ff590d 100644
--- a/zkvms/README.md
+++ b/zkvms/README.md
@@ -20,7 +20,7 @@ To make input and output handling generic, we define a guest "wrapper" crate ins
We need to be extra generic in our guest wrapper, because the type of our input function (and therefore, our information on what we need to do) exists only in the user's guest implementation.
That is the reason why every guest must include a `#[guests_macro::proving_entrypoint]` attribute above their main function: it extracts that type and converts it into an "object" which can then be used inside the wrapper.
-That is also the reason why reading input and outputing the result is handled by `wrapper_macro`.
+That is also the reason why reading input and outputting the result is handled by `wrapper_macro`.
> [!NOTE]
> You may be tempted to think about using Rust generics, but in our case we can have: