diff --git a/pages/en/querying/graphql-api.mdx b/pages/en/querying/graphql-api.mdx
index e74a6e05c1ff..986d7bf15c35 100644
--- a/pages/en/querying/graphql-api.mdx
+++ b/pages/en/querying/graphql-api.mdx
@@ -205,7 +205,7 @@ _change_block(number_gte: Int)
 
 ### Time-travel queries
 
-You can query the state of your entities not just for the latest block, which is the by default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries.
+You can query the state of your entities not just for the latest block, which is the default, but also for an arbitrary block in the past. The block at which a query should happen can be specified either by its block number or its block hash by including a `block` argument in the toplevel fields of queries.
 
 The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the Ethereum chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.