Skip to content

fixed internal link and typos #571

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

Merged
merged 4 commits into from
Dec 14, 2020
Merged

fixed internal link and typos #571

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
afe714d
fixed internal link and typos
macfarla Dec 14, 2020
d31afb1
plurals
macfarla Dec 14, 2020
c1a330d
plural
macfarla Dec 14, 2020
ad3d99e
Merge branch 'master' into admin-account
NicolasMassart Dec 14, 2020
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
8 changes: 4 additions & 4 deletions docs/HowTo/Limit-Access/Updating-Permission-Lists.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,12 @@ description: Updating Hyperledger Besu onchain allowlists

# Updating nodes and accounts allowlists

## Update nodes allowlists
## Update nodes allowlist

To add a node to the Hyperledger Besu nodes allowlist:

1. On the _Nodes_ tab of the Permissioning Management Dapp, click the
_Add Nodes_ button. The Add Node window displays.
_Add Node_ button. The Add Node window displays.
1. Enter the [enode URL](../../Concepts/Node-Keys.md#enode-url) of the node you are adding and
click the _Add Node_ button.

Expand All @@ -22,7 +22,7 @@ To remove a node from the nodes allowlist:
!!! tip

If you add a running node, the node does not attempt to reconnect to the bootnode and
synchronize until peer discovery restarts. To add a allowlisted node as a peer without waiting
synchronize until peer discovery restarts. To add an allowlisted node as a peer without waiting
for peer discovery to restart, use
[`admin_addPeer`](../../Reference/API-Methods.md#admin_addpeer).

Expand All @@ -38,7 +38,7 @@ To remove a node from the nodes allowlist:
correctly configured for all nodes with the
externally accessible address.

## Update account allowlists
## Update accounts allowlist

To add an account to the accounts allowlist:

Expand Down
6 changes: 3 additions & 3 deletions docs/Tutorials/Permissioning/Getting-Started-Onchain-Permissioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,7 +192,7 @@ The migration logs the addresses of the Admin and Rules contracts.

!!! note

Only [admin accounts] can add or remove nodes from the permission list.
Only an [admin account] can add or remove nodes from the allowlist.

## Add the first node to the allowlist

Expand All @@ -202,5 +202,5 @@ The first node must [add itself to the allowlist] before adding other nodes.
[Start first node with onchain permissioning and the JSON-RPC HTTP service enabled]: #onchain-permissioning-command-line-options
[Clone the permissioning contracts repository and install dependencies]: #clone-the-contracts-and-install-dependencies
[Start the webserver for the Permissioning Management Dapp]: #start-the-webserver-for-the-permissioning-management-dapp
[add itself to the allowlist]: ../../HowTo/Limit-Access/Updating-Permission-Lists.md#update-node-permission-lists
[admin accounts]: ../../HowTo/Limit-Access/Updating-Permission-Lists.md#update-node-permission-lists
[add itself to the allowlist]: ../../HowTo/Limit-Access/Updating-Permission-Lists.md#update-nodes-allowlist
[admin account]: ../../HowTo/Limit-Access/Updating-Permission-Lists.md#update-nodes-allowlist