From c0f7f973d588bae0ef37aefbac34968271fd83b9 Mon Sep 17 00:00:00 2001 From: ludamad Date: Mon, 23 Sep 2024 17:05:56 -0400 Subject: [PATCH] chore(typo): build in => builtin --- .../developers/docs/nodes-and-clients/bootnodes/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/content/developers/docs/nodes-and-clients/bootnodes/index.md b/public/content/developers/docs/nodes-and-clients/bootnodes/index.md index cc544f7de49..0a3da8ebdfd 100644 --- a/public/content/developers/docs/nodes-and-clients/bootnodes/index.md +++ b/public/content/developers/docs/nodes-and-clients/bootnodes/index.md @@ -8,7 +8,7 @@ When a new node joins the Ethereum network it needs to connect to nodes that are ## Connect to a bootnode {#connect-to-a-bootnode} -Most clients have a list of bootnodes build in, but you might also want to run your own bootnode, or use one that is not part of the client's hardcoded list. In this case, you can specify them when starting your client, as follows (example is for Geth, please check your client's documentation): +Most clients have a list of bootnodes builtin, but you might also want to run your own bootnode, or use one that is not part of the client's hardcoded list. In this case, you can specify them when starting your client, as follows (example is for Geth, please check your client's documentation): ``` geth --bootnodes "enode://@:"