Match order of clients in ethd config

website/docs/About/Clients.mdx

@@ -10,27 +10,20 @@ directly from docker hub or github, respectively. In most cases, binary is the d
 Currently supported consensus clients:
 - [Lodestar](https://github.com/ChainSafe/lodestar)
 - [Nimbus](https://github.com/status-im/nimbus-eth2)
-- [Teku](https://github.com/Consensys/teku)
 - [Grandine](https://github.com/grandinetech/grandine)
+- [Teku](https://github.com/Consensys-Incorporated/teku)
+- [Prysm](https://github.com/OffchainLabs/prysm)
 - [Lighthouse](https://github.com/sigp/lighthouse)
-- [Prysm](https://github.com/prysmaticlabs/prysm)
+- [Caplin](https://github.com/erigontech/erigon)
 
 Currently supported execution clients:
+- [Ethrex](https://github.com/lambdaclass/ethrex)
+- [Nethermind](https://github.com/nethermindeth/nethermind)
 - [Reth](https://github.com/paradigmxyz/reth)
-- [Besu](https://github.com/hyperledger/besu)
-- [Nethermind](https://github.com/NethermindEth/nethermind)
+- [Besu](https://github.com/besu-eth/besu)
 - [Geth](https://github.com/ethereum/go-ethereum)
-- [Erigon](https://github.com/ledgerwatch/erigon)
-- [Ethrex](https://github.com/lambdaclass/ethrex)
+- [Erigon](https://github.com/erigontech/erigon)
 - [Nimbus EL](https://github.com/status-im/nimbus-eth1)
 
 > An Ethereum node has one consensus client and one execution client. Eth Docker can be used to split this between two
 machines, but that distributed setup is rare
-
-Currently supported additional options:
-- Sending stats to https://beaconcha.in
-- Prysm Web UI
-- Grafana dashboard
-- slasher - running slasher is optional and requires additional resources
-
-Please see [Prysm Web](../Usage/WebUI.mdx) for Web UI support on Prysm.

website/docs/About/Overview.mdx

@@ -39,8 +39,7 @@ An Ethereum staking full node has many moving parts. Here's a high level, concep
 
 ## Eth Docker feature highlights
 
-- Supports all FOSS (Free and Open Source Software) Ethereum clients in any combination: Lodestar, Nimbus, Teku,
-Grandine, Lighthouse, Prysm; and Nethermind, Besu, Reth, Erigon, Geth, Ethrex, Nimbus-EL
+- Supports all FOSS (Free and Open Source Software) Ethereum clients in any combination
 - Runs on Linux or macOS, Intel/AMD x64 or ARM or RISC-V CPUs
 - Supports running Ethereum nodes, staking or RPC, on Ethereum and Gnosis Chain; supports running ssv.network DVT
 nodes; supports integration with RocketPool in (reverse) hybrid mode

website/docs/Usage/Advanced/ClientSetup.mdx

@@ -15,18 +15,18 @@ Please choose:
 * The consensus client you wish to run
   * Lodestar
   * Nimbus
-  * Teku
   * Grandine
-  * Lighthouse
+  * Teku
   * Prysm
+  * Lighthouse
   * Caplin - built into Erigon
 * Your execution client you wish to run
+  * Ethrex
+  * Nethermind
   * Reth
   * Besu
-  * Nethermind
   * Geth
   * Erigon
-  * Ethrex
   * Nimbus EL
 * Whether to run a Grafana dashboard for monitoring
 
@@ -62,23 +62,23 @@ the file names.
 
 Choose one consensus client:
 
-- `teku.yml` - Teku
 - `lodestar.yml` - Lodestar
 - `nimbus.yml` - Nimbus
-- `lighthouse.yml` - Lighthouse
-- `prysm.yml` - Prysm
 - `grandine-allin1.yml` - Grandine
 - `grandine-plugin-allin1.yml` - Grandine integrated into Nethermind
+- `teku.yml` - Teku
+- `prysm.yml` - Prysm
+- `lighthouse.yml` - Lighthouse
 - `caplin.yml` - Caplin integrated into Erigon
 
 Choose one execution client:
 
+- `ethrex.yml` - Ethrex execution client
+- `nethermind.yml` - Nethermind
 - `reth.yml` - Reth
 - `besu.yml` - Besu
-- `nethermind.yml` - Nethermind
-- `erigon.yml` - Erigon execution client
 - `geth.yml` - Geth execution client
-- `ethrex.yml` - Ethrex execution client
+- `erigon.yml` - Erigon execution client
 - `nimbus-el.yml` - Nimbus execution client
 
 > If you wish to use the built-in Caplin consensus client with Erigon, use `erigon.yml` without a consensus client file,