From c4614f975225e35162979df40821ff40d8d6a737 Mon Sep 17 00:00:00 2001 From: Bryer <0xbryer@gmail.com> Date: Sun, 17 Nov 2024 11:54:29 +0200 Subject: [PATCH 1/2] Typo Update proof-of-stake-devnet.md The word "require" should be "requires" to match the singular subject "node." --- 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 0270c8dba..8e5efb521 100644 --- a/website/docs/advanced/proof-of-stake-devnet.md +++ b/website/docs/advanced/proof-of-stake-devnet.md @@ -24,7 +24,7 @@ Notwithstanding, more complex applications may want an environment that is close ## Setting up -Today, running an Ethereum node require **two components**: +Today, running an Ethereum node requires **two components**: 1. **execution client software** in charge of processing transactions and smart contracts. Example of execution client softwares are: [go-ethereum](https://geth.ethereum.org), [besu](https://besu.hyperledger.org/), [erigon](https://github.com/ledgerwatch/erigon), [nethermind](https://nethermind.io/) or [reth](https://paradigmxyz.github.io/reth/). 2. **consensus client software** in charge of running the proof-of-stake logic. This tutorial will use the [Prysm](https://github.com/prysmaticlabs/prysm) implementation, which my team develops. From 8779f571c5a7181455e7efe0c272f78e2c3be409 Mon Sep 17 00:00:00 2001 From: Bryer <0xbryer@gmail.com> Date: Sun, 17 Nov 2024 11:56:21 +0200 Subject: [PATCH 2/2] Typo Update switch-clients.md The word "port forwards" should be "port forwarding," as it refers to the process, not a plural item. --- website/docs/advanced/switch-clients.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/switch-clients.md b/website/docs/advanced/switch-clients.md index ff70c828b..37f97c964 100644 --- a/website/docs/advanced/switch-clients.md +++ b/website/docs/advanced/switch-clients.md @@ -51,7 +51,7 @@ We have a section dedicated to exporting and importing slashing protection histo This step is not required for nodes which are running on a virtual public cloud, but keep in mind - nodes will be required to run a an execution client locally post merge! -By default, Prysm uses TCP/13000 and UDP/12000. Remove those two rules and replace them with the appropriate port forwards for the client you are switching to. The process will be very similar to the steps laid out [here.](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#port-forwarding) +By default, Prysm uses TCP/13000 and UDP/12000. Remove those two rules and replace them with the appropriate port forwarding for the client you are switching to. The process will be very similar to the steps laid out [here.](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#port-forwarding) Teku, Nimbus, and Lighthouse all use port 9000 for both TCP and UDP.