Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: typos in documentation files #986

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

fix: typos in documentation files #986

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b501a21
Update web3signer.md
leopardracer Nov 10, 2024
d84671c
Update end-to-end.md
leopardracer Nov 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/devtools/end-to-end.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ import {HeaderBadgesWidget} from '@site/src/components/HeaderBadgesWidget.js';

<HeaderBadgesWidget />

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 consists 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

Expand Down
4 changes: 2 additions & 2 deletions website/docs/wallet/web3signer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ import {HeaderBadgesWidget} from '@site/src/components/HeaderBadgesWidget.js';

Web3Signer follows the [Remote Signing API](https://github.com/ethereum/remote-signing-api) specification.

Prysm supports the use of Web3Signer the following flags:
Prysm supports the use of Web3Signer with the following flags:

`--validators-external-signer-url` : base URL for the Web3Signer.

Expand Down Expand Up @@ -115,4 +115,4 @@ Keys updated via the Remote Keymanager API will be persisted to the file as a he

If the file is removed or the file is empty, the validator will revert to the public keys set via the `--validators-external-signer-public-keys` flag.

On restart, the validator will read the file and set the public keys from the file.
On restart, the validator will read the file and set the public keys from the file.