diff --git a/linkerd.io/content/blog/accelerate-linker-with-dlb.md b/linkerd.io/content/blog/accelerate-linker-with-dlb.md
index f4dd22310f..8331fb5b2f 100644
--- a/linkerd.io/content/blog/accelerate-linker-with-dlb.md
+++ b/linkerd.io/content/blog/accelerate-linker-with-dlb.md
@@ -75,7 +75,7 @@ In this way, the workload of all threads can be balanced by Intel DLB and perfec
 The best case for Intel DLB-enabled Tokio is high traffic, like ingress. Since Linkerd2 should work with existing ingress solutions such as Nginx Ingress, we deploy the benchmark environment as below:
 ![dlb-benchmark-env](/uploads/dlb-benchmark-env.png)
 
-In our lab, we compared the baseline of pure Linkerd2-Proxy to the target of Linkerd2-Proxy plus Intel DLB. The result shows that the request per second has been greatly improved and the latency has been reduced.
+In our lab, we compared the baseline of pure Linkerd2-Proxy to the target of Linkerd2-Proxy plus Intel DLB and the result shows that the request per second has been improved and the latency has been reduced.
 
 ## Conclusion
 
@@ -85,4 +85,4 @@ The fourth-generation Intel Xeon scalable processor, codenamed Sapphire Rapids,
 
 The whole solution is experimental, please contact [me](mailto:loong.dai@intel.com) for any details if interested.
 
-We firmly believe that with the development of cloud computing and service mesh, solutions combining software and hardware can provide users with higher performance.
\ No newline at end of file
+We firmly believe that with the development of cloud computing and service mesh, solutions combining software and hardware can provide users with higher performance.