diff --git a/docs/build/getting-started/networks-endpoints.mdx b/docs/build/getting-started/networks-endpoints.mdx
index d295b636bc8..8f8db9f08d4 100644
--- a/docs/build/getting-started/networks-endpoints.mdx
+++ b/docs/build/getting-started/networks-endpoints.mdx
@@ -30,6 +30,12 @@ have more control and to not run into any limits.
 [The IOTA Mainnet](https://explorer.iota.org/mainnet) is the production network within the IOTA ecosystem using the IOTA
 token.
 
+:::info
+
+This network runs under a [Coordinator PoA scheme](/learn/protocols/coordinator/) with validators operated by [Akkodis](https://www.akkodis.com), [ETO GRUPPE](https://www.etogruppe.com/), [Software AG](https://softwareag.com/), [University of Zurich](https://www.uzh.ch/cmsssl/en.html), [Imperial College London](https://www.imperial.ac.uk) and the IOTA Foundation.
+
+:::
+
 | Base Token | Protocol | HTTP REST API                               | Event API                                                       | Permanode API                                     |
 | ---------- | -------- | ------------------------------------------- | --------------------------------------------------------------- | ------------------------------------------------- |
 | IOTA Token | Stardust | https://api.stardust-mainnet.iotaledger.net | wss://api.stardust-mainnet.iotaledger.net:443 (MQTT 3.1, /mqtt) | https://chronicle.stardust-mainnet.iotaledger.net |
diff --git a/docs/learn/protocols/coordinator.md b/docs/learn/protocols/coordinator.md
index 915ef513569..11bc1ab6c2e 100644
--- a/docs/learn/protocols/coordinator.md
+++ b/docs/learn/protocols/coordinator.md
@@ -9,21 +9,31 @@ keywords:
 # The Coordinator - PoA Consensus
 
 :::note
+
 The Coordinator is a temporary feature running under the Chrysalis and Stardust protocol versions
 and will be removed with the upcoming IOTA 2.0 update.
+
 :::
 
-The Coordinator is a node controlled by the IOTA Foundation that sends signed blocks called milestones that nodes trust
-and use to confirm blocks and reach _consensus_. Blocks which are directly or indirectly referenced by a milestone block
+The Coordinator is a [node plugin](https://github.com/iotaledger/inx-tendercoo) that sends signed blocks called milestones that nodes trust
+and use to confirm blocks and reach _consensus_. Blocks that are directly or indirectly referenced by a milestone block
 are automatically deemed confirmed, though whether they mutate the ledger depends on the [White-Flag consensus](/learn/protocols/chrysalis/core-concepts/white-flag-consensus)
-approach. Before the [White-Flag consensus](/learn/protocols/chrysalis/core-concepts/white-flag-consensus) was introduced, nodes would instead compute mutations via cumulative weight
-calculations.
+approach.
+The current Coordinator is based on the Tendermint Core BFT consensus, which enables a committee of validators to operate as a distributed Coordinator.
+
+:::info
+
+In the current Shimmer network, all instances of the Coordinator are run by the IOTA Foundation. In the IOTA Mainnet they are run by [Akkodis](https://www.akkodis.com), [ETO GRUPPE](https://www.etogruppe.com/), [Software AG](https://softwareag.com/), [University of Zurich](https://www.uzh.ch/cmsssl/en.html), [Imperial College London](https://www.imperial.ac.uk) and the IOTA Foundation.
+
+:::
 
 :::note
+
 Even though the Coordinator acts as a centralized _confirmation_ device or finality gadget, it is not able to move or
 alter the ledger in any other way than given by the user issued transactions in the _DAG_. Therefore, the Coordinator
 can only censor transactions (which would be more visible than in traditional blockchains) but not actively mint or
 remove tokens from the ledger.
+
 :::
 
 Nodes within an IOTA network running under PoA via the Coordinator have its public keys saved in the configuration and