fix: forgot to update a number

blog/2024-01-22-echo-v1-release/index.md

@@ -22,7 +22,7 @@ The internal propagation is handled through a private link, which ensures that t
 In the above example, Bob from the United States is trying to send a bundle to a block builder in Europe. The two alternative paths are:
 
 - **The builder's own RPC API (the orange line)**: direct connection with 150ms latency. In normal circumstances, the request will be routed through the public internet, which entails a relatively high latency when compared to datacenter-to-datacenter peerings.
-- **Echo V1.0 (the blue path)**: A sum of three components: 20ms for the request to the closest Echo node, then 45ms of internal propagation time to reach the Echo node in Europe, and finally 10ms for the last leg to reach the block builder. This totals 75ms, which is 80ms faster than the direct connection in this specific example.
+- **Echo V1.0 (the blue path)**: A sum of three components: 20ms for the request to the closest Echo node, then 45ms of internal propagation time to reach the Echo node in Europe, and finally 10ms for the last leg to reach the block builder. This totals 75ms, which is 75ms faster than the direct connection in this specific example.
 
 Of course, the actual latency will vary depending on the user's location and the block builder's own optimizations. However, Echo V1.0 will always try to find the fastest path to the block builder.