diff --git a/docs/aggregations.md b/docs/aggregations.md
index 301bb70c659..90b3b5ce109 100644
--- a/docs/aggregations.md
+++ b/docs/aggregations.md
@@ -141,7 +141,7 @@ The following aggregation functions are currently supported:
 
 The `first` and `last` aggregation function calculate the first and last
 value in an interval by sorting the data by `id`; `graph-node` enforces
-correctness here by automatically setting the `id` for timeseries entities.
+correctness hereby automatically setting the `id` for timeseries entities.
 
 #### Aggregation expressions
 
diff --git a/docs/implementation/metadata.md b/docs/implementation/metadata.md
index 562bc371e71..fb1d6c08d71 100644
--- a/docs/implementation/metadata.md
+++ b/docs/implementation/metadata.md
@@ -144,7 +144,7 @@ should have the 'account-like' optimization turned on.
 
 ### `subgraphs.subgraph_features`
 
-Details about features that a deployment uses, Maintained in the primary.
+Details about features that a deployment uses are maintained in the primary.
 
 | Column         | Type      | Use         |
 |----------------|-----------|-------------|
diff --git a/docs/implementation/sql-query-generation.md b/docs/implementation/sql-query-generation.md
index e88602a26fe..9bfc971aab6 100644
--- a/docs/implementation/sql-query-generation.md
+++ b/docs/implementation/sql-query-generation.md
@@ -300,7 +300,7 @@ from the database is that it is impossible with Diesel to execute queries
 where the number and types of the columns of the result are not known at
 compile time.
 
-We need to to be careful though to not convert to JSONB too early, as that
+We need to be careful though to not convert to JSONB too early, as that
 is slow when done for large numbers of rows. Deferring conversion is
 responsible for some of the complexity in these queries.