diff --git a/blog/2024/August/why-meshtastic-uses-managed-flood-router.mdx b/blog/2024/August/why-meshtastic-uses-managed-flood-router.mdx
index 341470b5..c14a483a 100644
--- a/blog/2024/August/why-meshtastic-uses-managed-flood-router.mdx
+++ b/blog/2024/August/why-meshtastic-uses-managed-flood-router.mdx
@@ -40,7 +40,7 @@ Furthermore, Managed Flood Routing is certainly scalable, because nodes that are
 ## Functions on Resource Constrained Devices
 Finally, Managed Flood Routing minimizes footprint on very resource-constrained low power IoT devices. Traditional routing algorithms often require devices to maintain large routing tables or perform complex calculations, consuming additional RAM, flash, and valuable computational resources. Managed Flood Routing, with its simplicity and distributed nature, significantly reduces the resource overhead. Devices only need to forward messages they receive, without the need for complex computations, resulting in more device resource availability for other valuable features and improved device autonomy.
 
-:::info Many decisions are based on empirical data from [Meshtasticator](https://github.com/GUVWAF/Meshtasticator) simulations
+:::info Many decisions are based on data from [Meshtasticator](https://github.com/GUVWAF/Meshtasticator) simulations
 ![Route Plot](/img/blog/route_plot.png)
 :::