diff --git a/docs/developers/index.md b/docs/developers/index.md index a444964083..5f505de416 100644 --- a/docs/developers/index.md +++ b/docs/developers/index.md @@ -35,4 +35,4 @@ Tracing allows developers to analyze precisely what the EVM has done or will do - [Basic tracers](/docs/developers/evm-tracing/basic-traces) - [Built-in tracers](/docs/developers/evm-tracing/built-in-tracers) - [Custom tracers](/docs/developers/evm-tracing/custom-tracer) -- [Javascript tracing tutorial](/docs/developers/evm-tracing/javascript-tutorial) \ No newline at end of file +- [Javascript tracing tutorial](/docs/developers/evm-tracing/javascript-tutorial) diff --git a/docs/faq.md b/docs/faq.md index a4e69a5d6c..b5466ba3d6 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -32,7 +32,7 @@ sudo ntpdate -s time.nist.gov ## I would like to run multiple Geth instances but got the error "Fatal: blockchain db err: resource temporarily unavailable". {#multiple-geth-instances} -Geth uses a datadir to store the blockchain, accounts and some additional information. This directory cannot be shared between running instances. If you would like to run multiple instances follow [these](/docs/developers/geth-developer/private-network) instructions. +Geth uses a datadir to store the blockchain, accounts and some additional information. This directory cannot be shared between running instances. If you would like to run multiple instances follow [these](/docs/fundamentals/private-network) instructions. ## When I try to use the --password command line flag, I get the error "Could not decrypt key with given passphrase" but the password is correct. Why does this error appear? {#could-not-decrypt-key} diff --git a/docs/fundamentals/index.md b/docs/fundamentals/index.md index d6a6bc0a1a..a15c709a47 100644 --- a/docs/fundamentals/index.md +++ b/docs/fundamentals/index.md @@ -24,4 +24,4 @@ Note also that there is a page explaining common log messages that are often que - [Pruning](/docs/fundamentals/pruning): read about Geth's data pruning options - [Private networks](/docs/fundamentals/private-network): learn hoe to set up a private network of multiple Geth nodes - [Light clients](/docs/fundamentals/les): read about Geth's light mode. -- [Mining](/docs/fundamentals/mining): read about the minign algorithms Geth used to use to secure Ethereum before the network switched to proof-of-stake. \ No newline at end of file +- [Mining](/docs/fundamentals/mining): read about the minign algorithms Geth used to use to secure Ethereum before the network switched to proof-of-stake. diff --git a/docs/fundamentals/peer-to-peer.md b/docs/fundamentals/peer-to-peer.md index ddfe0e52e2..9867f3a81c 100644 --- a/docs/fundamentals/peer-to-peer.md +++ b/docs/fundamentals/peer-to-peer.md @@ -3,7 +3,7 @@ title: Connecting To The Network description: Guide to connecting Geth to a peer-to-peer network --- -The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/developers/geth-developer/private-network) and [local testnets](/docs/developers/geth-developer/dev-mode). For convenience, the two public testnets with long term support, Goerli and Sepolia, have their own command line flag. Geth can connect to these testnets simply by passing: +The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/fundamentals/private-network) and [local testnets](/docs/developers/geth-developer/dev-mode). For convenience, the two public testnets with long term support, Goerli and Sepolia, have their own command line flag. Geth can connect to these testnets simply by passing: - `--goerli`, Goerli proof-of-authority test network - `--sepolia` Sepolia proof-of-work test network @@ -106,7 +106,7 @@ The `admin` module also includes functions for gathering information about the l ## Custom Networks {#custom-networks} -It is often useful for developers to connect to private test networks rather than public testnets or Ethereum mainnet. These sandbox environments allow block creation without competing against other miners, easy minting of test ether and give freedom to break things without real-world consequences. A private network is started by providing a value to `--networkid` that is not used by any other existing public network ([Chainlist](https://chainlist.org)) and creating a custom `genesis.json` file. Detailed instructions for this are available on the [Private Networks page](/docs/developers/geth-developer/private-network). +It is often useful for developers to connect to private test networks rather than public testnets or Ethereum mainnet. These sandbox environments allow block creation without competing against other miners, easy minting of test ether and give freedom to break things without real-world consequences. A private network is started by providing a value to `--networkid` that is not used by any other existing public network ([Chainlist](https://chainlist.org)) and creating a custom `genesis.json` file. Detailed instructions for this are available on the [Private Networks page](/docs/fundamentals/private-network). ## Static nodes {#static-nodes} diff --git a/docs/fundamentals/security.md b/docs/fundamentals/security.md index bd6cbc06c6..d8807b74cf 100644 --- a/docs/fundamentals/security.md +++ b/docs/fundamentals/security.md @@ -25,4 +25,4 @@ Geth has built-in account management tools. However, Clef is recommended as an e ## Other security considerations {#other-security} -Even with a perfectly secure node, users can still be manipulated by attackers into exposing security weaknesses or inadvertently interact with insecure smart contracts. For an overview, please see the Ethereum [security best practise webpage](https://ethereum.org/en/security) and this introduction to [smart contract security](https://ethereum.org/en/developers/docs/smart-contracts/security). +Even with a perfectly secure node, users can still be manipulated by attackers into exposing security weaknesses or inadvertently interact with insecure smart contracts. For an overview, please see the Ethereum [security best practice webpage](https://ethereum.org/en/security) and this introduction to [smart contract security](https://ethereum.org/en/developers/docs/smart-contracts/security). diff --git a/docs/tools/clef/clique-signing.md b/docs/tools/clef/clique-signing.md index 21f773cc05..b9aa2f6113 100644 --- a/docs/tools/clef/clique-signing.md +++ b/docs/tools/clef/clique-signing.md @@ -11,7 +11,7 @@ Clef provides a way to safely circumvent `--unlock` while maintaining a enough a ## Prerequisites {#prerequisites} -It is useful to have basic knowledge of private networks and Clef. These topics are covered on our [private networks](/docs/developers/geth-developer/private-network) and [Introduction to Clef](/docs/tools/clef/introduction) pages. +It is useful to have basic knowledge of private networks and Clef. These topics are covered on our [private networks](/docs/fundamentals/private-network) and [Introduction to Clef](/docs/tools/clef/introduction) pages. ## Prepping a Clique network {#prepping-clique-network} diff --git a/redirects.js b/redirects.js index 2e05264b86..fdd78cc0b0 100644 --- a/redirects.js +++ b/redirects.js @@ -278,6 +278,11 @@ const redirects = [ source: '/docs/tools', destination: '/docs/tools/clef/introduction', permanent: true + }, + { + source: '/docs/tools/clef', + destination: '/docs/tools/clef/introduction', + permanent: true } ];