diff --git a/website/docs/maintenance/tiered-storage/overview.md b/website/docs/maintenance/tiered-storage/overview.md
index 8e0f251d..7517b35e 100644
--- a/website/docs/maintenance/tiered-storage/overview.md
+++ b/website/docs/maintenance/tiered-storage/overview.md
@@ -5,14 +5,14 @@ sidebar_position: 1
 # Overview
 
 With tiered storage, Fluss allows you to scale compute and storage resources independently, provides better client isolation, and
-allow faster maintenance.
+allows faster maintenance.
 
-Fluss organize data into different storage layers based on its access patterns, performance requirements, and cost considerations.
+Fluss organizes data into different storage layers based on its access patterns, performance requirements, and cost considerations.
 
-Fluss ensures the recent data is stored in local for higher write/read performance and the historically data is stored in [remote storage](remote-storage.md) for lower cost.
+Fluss ensures the recent data is stored in local for higher write/read performance and the historical data is stored in [remote storage](remote-storage.md) for lower cost.
 
 What's more, since the native format of Fluss's data is optimized for real-time write/read which is inevitable unfriendly to batch analytics, Fluss also introduces a [lakehouse storage](lakehouse-storage.md) which stores the data
-in the well-known open data lake format for better analytics performance. Currently, only Paimon is supported, but more kinds of data lake support are on the ways. Keep eyes on us!
+in the well-known open data lake format for better analytics performance. Currently, only Paimon is supported, but more kinds of data lake support are on the way. Keep eyes on us!
 
 The overall tiered storage architecture is shown in the following diagram: