diff --git a/crates/db_views/src/post_view.rs b/crates/db_views/src/post_view.rs
index 14a9b4f81..afb0f435f 100644
--- a/crates/db_views/src/post_view.rs
+++ b/crates/db_views/src/post_view.rs
@@ -652,7 +652,7 @@ impl<'a> PostQuery<'a> {
     pool: &mut DbPool<'_>,
   ) -> Result<Option<PostQuery<'a>>, Error> {
     // first get one page for the most popular community to get an upper bound for the page end for
-    // the real query the reason this is needed is that when fetching posts for a single
+    // the real query. the reason this is needed is that when fetching posts for a single
     // community PostgreSQL can optimize the query to use an index on e.g. (=, >=, >=, >=) and
     // fetch only LIMIT rows but for the followed-communities query it has to query the index on
     // (IN, >=, >=, >=) which it currently can't do at all (as of PG 16). see the discussion