From 42444856d444e47333247f291229a5a61abb6cf5 Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 19 Jul 2024 18:06:57 +0300 Subject: [PATCH 1/3] correct pronoun usage proof-of-stake-devnet.md --- website/docs/advanced/proof-of-stake-devnet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/proof-of-stake-devnet.md b/website/docs/advanced/proof-of-stake-devnet.md index d903f9623..e5c05ff60 100644 --- a/website/docs/advanced/proof-of-stake-devnet.md +++ b/website/docs/advanced/proof-of-stake-devnet.md @@ -18,7 +18,7 @@ With Ethereum having finally transitioned to proof-of-stake, many people are won Running nodes has become easier over the past few years, with go-ethereum taking around 1 day to sync and some hyper-optimized clients such Reth or Erigon taking less than a week to sync an entire, _archival_ node. It is true that setting up a node on mainnet today is easier than ever. However, developers often want to set up their own, local blockchain for testing purposes. We call these **development networks** or **devnets**. -Devnets are critical for developers working on the protocol as well as smart contract developers that want to run their own chain using their own initial state. However, the latter need can be satisfied by tools such as [Foundry](https://github.com/foundry-rs/foundry/) which runs a “simulated” Ethereum environment that is enough for testing many contract interactions. +Devnets are critical for developers working on the protocol as well as smart contract developers who want to run their own chain using their own initial state. However, the latter need can be satisfied by tools such as [Foundry](https://github.com/foundry-rs/foundry/) which runs a “simulated” Ethereum environment that is enough for testing many contract interactions. Notwithstanding, more complex applications may want an environment that is closer to a **real Ethereum blockchain**, and setting up a local chain from scratch is the best approach. This section will help you understand how to set up your own, **local Ethereum chain** from scratch. From f62cf42885c1a924e6e04184a832fc1f798544d3 Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 19 Jul 2024 18:09:16 +0300 Subject: [PATCH 2/3] fix spelling bugreports.md --- website/docs/contribute/bugreports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/contribute/bugreports.md b/website/docs/contribute/bugreports.md index 122d137f1..f2f6459e7 100644 --- a/website/docs/contribute/bugreports.md +++ b/website/docs/contribute/bugreports.md @@ -14,7 +14,7 @@ Bug reports are critical to the rapid development of the Prysm client. In order Duplicate tickets are a hinderance to the development process and, as such, it is crucial to first check through Prysm's existing issues to see if what you are experiencing has already been indexed. -To do so, head over to the [issue page](https://github.com/prysmaticlabs/prysm/issues) and enter some related keywords into the search bar. This may include a sample from the output or specific components it affects. If this is unsuccessful, check the [issue labels index](https://github.com/prysmaticlabs/prysm/labels) for related catagories and review the tickets within. +To do so, head over to the [issue page](https://github.com/prysmaticlabs/prysm/issues) and enter some related keywords into the search bar. This may include a sample from the output or specific components it affects. If this is unsuccessful, check the [issue labels index](https://github.com/prysmaticlabs/prysm/labels) for related categories and review the tickets within. If searches have shown the issue in question has not been reported yet, feel free to open up a new issue ticket. From 6bedba1c9746ab35475ea1569eb6c91f4c02b399 Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 19 Jul 2024 18:10:54 +0300 Subject: [PATCH 3/3] correct form verb use end-to-end.md --- website/docs/devtools/end-to-end.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/devtools/end-to-end.md b/website/docs/devtools/end-to-end.md index 4b5190f68..a8190ebbf 100644 --- a/website/docs/devtools/end-to-end.md +++ b/website/docs/devtools/end-to-end.md @@ -8,7 +8,7 @@ import {HeaderBadgesWidget} from '@site/src/components/HeaderBadgesWidget.js'; -Even the best unit tests won't prevent bugs from creeping into the system. They test small pieces of code in isolation, but it might be the interaction between different modules/packages/subsystems that causes issues. Prysm consist of two separate components, the beacon chain and the validator, that interact with each other in non-trivial ways. Additionally, the system contacts an Eth1 endpoint to access various information about the Eth1 chain. It is therefore very important to find integration bugs as soon as possible. The way Prysm achieves this is through having an E2E (end-to-end) test module. Tests inside this module are ran on every PR build, which greatly increases confidence that new code can safely be merged. +Even the best unit tests won't prevent bugs from creeping into the system. They test small pieces of code in isolation, but it might be the interaction between different modules/packages/subsystems that causes issues. Prysm consist of two separate components, the beacon chain and the validator, that interact with each other in non-trivial ways. Additionally, the system contacts an Eth1 endpoint to access various information about the Eth1 chain. It is therefore very important to find integration bugs as soon as possible. The way Prysm achieves this is through having an E2E (end-to-end) test module. Tests inside this module are run on every PR build, which greatly increases confidence that new code can safely be merged. ## Running E2E tests