From ad14a9be7e933d61dbc1be138e1fb6ff29ebc6b6 Mon Sep 17 00:00:00 2001 From: m4sterbunny Date: Mon, 22 Jul 2024 15:03:40 +0100 Subject: [PATCH] Update docs/public-networks/how-to/connect/manage-peers.md proof Co-authored-by: Alexandra Carrillo <12214231+alexandratran@users.noreply.github.com> Signed-off-by: m4sterbunny --- docs/public-networks/how-to/connect/manage-peers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/public-networks/how-to/connect/manage-peers.md b/docs/public-networks/how-to/connect/manage-peers.md index 0b23f6c7a6b..768b904d0c0 100644 --- a/docs/public-networks/how-to/connect/manage-peers.md +++ b/docs/public-networks/how-to/connect/manage-peers.md @@ -75,7 +75,7 @@ To reduce the maximum number of peers, use the [`--max-peers`](../../reference/c ## Allowlist peers -You can can define specific IP subnets permitted to interact with the node using the [`--net-restrict`](../../reference/cli/options.md#net-restrict) configuration. This restricts access to only those peers whose IP addresses fall within the allowed subnets. This is particularly useful if you maintain a set of nodes and want to restrict which of those may connect to external nodes. +You can can define specific IP subnets permitted to interact with the node using the [`--net-restrict`](../../reference/cli/options.md#net-restrict) configuration. This restricts access to only those peers whose IP addresses fall within the allowed subnets. This is useful if you maintain a set of nodes and want to restrict which of those can connect to external nodes. ## Limit remote connections