diff --git a/src/pages/about-netbird/how-netbird-works.mdx b/src/pages/about-netbird/how-netbird-works.mdx
index a674cff5..b3ba64e6 100644
--- a/src/pages/about-netbird/how-netbird-works.mdx
+++ b/src/pages/about-netbird/how-netbird-works.mdx
@@ -24,7 +24,7 @@ It can be a Linux server running in the cloud or on-premises, a personal laptop,
With NetBird clients installed and authorized on the Management service, machines form a mesh network connecting to each other directly via an encrypted point-to-point Wireguard tunnel.
-
+
While it is possible to create a full mesh network, it might be not a desirable outcome. In this case, [ACLs](/how-to/manage-network-access) can be utilized to limit the access to certain machines.
@@ -54,7 +54,7 @@ After that, they are able to establish a connection to the new peer.
The Management service runs in the cloud NetBird-managed. It can also be self-hosted.
-
+
### Client Application
@@ -88,7 +88,7 @@ The only Signal's responsibility is:
This is done through Signal. After a connection has been established, Signal steps out.
-
+
@@ -105,7 +105,7 @@ In fact, we use an open-source implementation called [Coturn](https://github.com
The purpose of this service is to be a "plan B" and relay traffic between peers in case a peer-to-peer connection isn't possible.
-
+