diff --git a/documentation/docs/pages/network/architecture/mixnet.mdx b/documentation/docs/pages/network/architecture/mixnet.mdx
index e272a5695e..3aa5bbe08d 100644
--- a/documentation/docs/pages/network/architecture/mixnet.mdx
+++ b/documentation/docs/pages/network/architecture/mixnet.mdx
@@ -4,7 +4,7 @@ The mixnet is made up of nodes running in several different roles:
 * **Gateways** act as message storage for clients which may go offline and come back online again, and (once zk-nyms are enabled) check for anonymous proof of access credentials. They represent the first and last hop Mixnet packets travel through when travelling between clients.
 * **Services** are applications that communicate with nym clients, listening and sending traffic to the mixnet. This is an umbrella term for a variety of different pieces of code, such as the Network Requester.
 
-* **Clients** are used to connect to and send messages through the Mixnet to other clients, utilising Gateways for ingress and egress.
+> **Clients** are used to connect to and send messages through the Mixnet to other clients, utilising Gateways for ingress and egress. These are however on the 'user' side and not a Mixnet component per se.
 
 ## Smoosh Status
 The various Mixnet components were originally completely separate binaries. They are in the process of being 'smooshed' together into a single `nym-node` binary which runs in different modes for ease of use, as well as to allow for a more developed and responsive Mixnet design, where the role of a node in a given time period is decided and changed automatically based on network conditions (more on this in the future).