Revise Running Nethermind instructions

docs/developers/building-from-source.md

@@ -53,7 +53,7 @@ configuration only.
 The build artifacts can be found in the `bin/release/net7.0` directory. By default, the logs and database directories
 are located here as well.
 
-For more info, see [Running Nethermind](../fundamentals/running-nethermind.md).
+For more info about launching Nethermind, see the [Launching](../get-started/installing-nethermind.md#launching) section.
 
 #### Testing
 

docs/fundamentals/private-networks.md

@@ -1,7 +1,7 @@
 ---
 title: Private networks
 description: Use Kurtosis to deploy a private Ethereum devnet with Nethermind and any consensus client at any scale you need, wherever you need it.
-sidebar_position: 8
+sidebar_position: 7
 ---
 
 This guide will walk you through using [Kurtosis `ethereum-package`](https://github.com/kurtosis-tech/ethereum-package) to spin up a private, proof-of-stake (PoS) Ethereum devnet with three full Ethereum nodes locally over Docker. At the end of the guide, you will learn how to scale up your testnet on Kubernetes as well as enable optional services for your local testnet, such as network observability tools (e.g., Grafana, Prometheus) and Flashbot's `mev-boost` infrastructure to simulate MEV workflows.

docs/fundamentals/pruning.md

@@ -1,6 +1,6 @@
 ---
 title: Pruning
-sidebar_position: 5
+sidebar_position: 6
 ---
 
 ## Overview

docs/get-started/consensus-clients.md

@@ -118,7 +118,7 @@ nethermind \
   --JsonRpc.JwtSecretFile path/to/jwt.hex
 ```
 
-The command above runs Nethermind on Mainnet. For other networks, set the `-c` option accordingly. For more info, see [Running Nethermind](../fundamentals/running-nethermind.md).
+The command above runs Nethermind on Mainnet. For other networks, set the `-c` option accordingly. For more info, see [Running Nethermind](../get-started/installing-nethermind.md#running).
 
 [checkpoint-sync-endpoints]: https://eth-clients.github.io/checkpoint-sync-endpoints
 [lighthouse]: https://lighthouse-book.sigmaprime.io

docs/get-started/installing-nethermind.md

@@ -116,7 +116,7 @@ brew install nethermind
 </TabItem>
 </Tabs>
 
-For further instructions, see [Running Nethermind](../fundamentals/running-nethermind.md).
+For further instructions, see [Running Nethermind](#running).
 
 ## Standalone downloads
 
@@ -193,7 +193,7 @@ To monitor the Nethermind output, run:
 journalctl -u nethermind -f
 ```
 
-For further instructions, see [Running Nethermind](../fundamentals/running-nethermind).
+For further instructions, see [Running Nethermind](#running).
 
 ## Docker container
 
@@ -250,9 +250,42 @@ docker run -it \
   nethermind/nethermind -dd /nethermind/data_dir
 ```
 
-Note that any Nethermind-specific configuration option can be specified at the end. For instance, the `-dd` option in this case.
+Note that any Nethermind-specific configuration option can be specified at the end. For instance, the `-dd` option in this case. For further instructions, see [Running Nethermind](#running).
 
-#### See also
+To build the Docker image yourself, see [Building Docker image](../developers/building-from-source.md#bulding-docker-image).
 
-- [Configuration options](../fundamentals/configuration.md)
-- [Building Docker image](../developers/building-from-source.md#bulding-docker-image)
+## Running Nethermind {#running}
+
+:::caution Important
+A [consensus client](consensus-clients.md) of your choice must be running before you start Nethermind.
+:::
+
+Nethermind is mainly controlled by command line options (aka arguments or flags).
+
+The full list of options can be displayed by running:
+
+```bash
+nethermind -h
+```
+
+For instance, to launch the client with the default configuration for the Mainnet and custom data directory, run:
+
+```bash
+nethermind -c mainnet -dd path/to/data/dir
+```
+
+For detailed info about the available configuration options, see [Configuration](./configuration.md).
+
+### Supported networks
+
+To run Nethermind on a specific network, use the [`-c, --config`](./configuration.md#basic-options) command line option. Currently, the following networks are supported out of the box:
+
+- **Chiado** (testnet)
+- **Energy Web**
+- **Exosama**
+- **Goerli** (testnet)
+- **Gnosis** 
+- **Holesky** (testnet)
+- **Mainnet**
+- **Sepolia** (testnet)
+- **Volta** (testnet)

docs/validators/aura-validator.md

@@ -5,7 +5,7 @@ sidebar_position: 1
 
 This article will lead you through docker-compose setup of **Nethermind Aura Validator** (xDai chain in this example).
 Same result can be obtained
-by [Downloading](../get-started/installing-nethermind.md) & [Running Nethermind](../fundamentals/running-nethermind.md)
+by [Downloading](../get-started/installing-nethermind.md) & [Running Nethermind](../get-started/installing-nethermind.md#running)
 package or by [Building Nethermind](../developers/building-from-source.md) from the source code. 
 
 If you chose not to use docker-compose, you can skip docker-compose related sections and read
@@ -105,8 +105,8 @@ container (`xdai.cfg` file in above example).
 Make sure that `nethermind_db`, `keystore`(`logs` - optional ) are mapped, otherwise you might lose database or keys
 :::
 
-[`NLog.config`](../fundamentals/running-nethermind.md) file is optional.\
-[`static-nodes.json`](../fundamentals/running-nethermind.md) can be filled with an
+[`NLog.config`](../get-started/installing-nethermind.md#running) file is optional.\
+[`static-nodes.json`](../get-started/installing-nethermind.md#running) can be filled with an
 array
 of enodes, this is also optional.