From c757193087accceff75e3a25a79167879e0adceb Mon Sep 17 00:00:00 2001 From: Collin Jackson Date: Mon, 21 Oct 2024 05:29:59 -0700 Subject: [PATCH] fix typo --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 843bd44..1346867 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,7 +41,7 @@ As a starting point, in a bug report we will pretty much always want: - the Nexus network version/revision you are using; - the platform you are on, ideally both the operating system (Windows, macOS, or Linux) and the machine architecture (_e.g.,_ if you're using an M-series Mac) if you know them; -- console logs from the CLI or web application showing errors ands status messages; +- console logs from the CLI or web application showing errors and status messages; - concrete and comprehensive steps to reproduce the bug. Code snippets should be as minimal as possible. It is always better if you can reproduce the bug with a small snippet that focuses on your Nexus zkVM usage rather than on the surrounding code in your project. This will help collaborators verify, reproduce, and zero in on a fix.