website: rename private-network to private-networks

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/fundamentals/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-networks) 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}
 

docs/fundamentals/index.md

@@ -22,6 +22,6 @@ Note also that there is a page explaining common log messages that are often que
 - [Logs](/docs/fundamentals/logs): learn how to interpret the main log messages Geth displays in the console
 - [Peer-to-peer](/docs/fundamentals/peer-to-peer): learn about Geth's peer-to-peer networking
 - [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
+- [Private networks](/docs/fundamentals/private-networks): 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 mining algorithms Geth used to use to secure Ethereum before the network switched to proof-of-stake.

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/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:
+The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/fundamentals/private-networks) 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/fundamentals/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-networks).
 
 ## Static nodes {#static-nodes}
 

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/fundamentals/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-networks) and [Introduction to Clef](/docs/tools/clef/introduction) pages.
 
 ## Prepping a Clique network {#prepping-clique-network}
 

docs/tools/puppeth.md

@@ -1,10 +1,10 @@
 ---
 title: Puppeth
-description: introduction to the private-network boot-strapping tool, Puppeth
+description: introduction to the private-networks boot-strapping tool, Puppeth
 ---
 
 <Note>Puppeth was [removed from Geth](https://github.com/ethereum/go-ethereum/pull/26581) in January 2023.</Note>
 
 Puppeth was a tool for quickly spinning up and managing private development networks. The user was guided through the process by a command line wizard instead of having to configure the network manually. However, this tool has been discontinued and removed from the Geth repository.
 
-Instructions for setting up a private network using Ethash or Clique are available on our [private networks page](/docs/fundamentals/private-network.md).
+Instructions for setting up a private network using Ethash or Clique are available on our [private networks page](/docs/fundamentals/private-networks).

src/data/documentation-links.yaml

@@ -33,7 +33,7 @@
     - id: Pruning
       to: /docs/fundamentals/pruning
     - id: Private networks
-      to: /docs/fundamentals/private-network
+      to: /docs/fundamentals/private-networks
     - id: Config files
       to: /docs/fundamentals/config-files
     - id: Light client