From cdb6f5889f0a6b57c5feba8706177ddb791073ca Mon Sep 17 00:00:00 2001
From: Andy Hattemer <&@ruf.io>
Date: Fri, 26 Mar 2021 11:36:45 -0400
Subject: [PATCH] Typo fixups (Matching with Materialize.com blog)

---
 posts/2020-12-29.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/posts/2020-12-29.md b/posts/2020-12-29.md
index 3fd3bb4..c8808d0 100644
--- a/posts/2020-12-29.md
+++ b/posts/2020-12-29.md
@@ -196,7 +196,7 @@ Expressing a request for a week-long interval would require 10,080 minutes as in
 
 However, no one said you had to use only minutes. Or only hours.
 You can cover most of your hypothetical week with daily aggregates, six at least.
-You can then just grab a few houly aggregates at each end, and a few minutely aggregates if you want those too.
+You can then just grab a few hourly aggregates at each end, and a few minutely aggregates if you want those too.
 
 Let's spell this out with an example, as it will be important to be clear.
 Let's say your request times are
@@ -239,7 +239,7 @@ We'll write some queries in the appendix that automatically produce these interv
 
 ---
 
-For now, let's imagine for now we have your request input in this more expansive representation.
+For now, let's imagine we have your request input in this more expansive representation.
 How might you get your aggregate results out?
 What SQL queries do we need to write to make that happen?
 
@@ -498,4 +498,4 @@ WHERE
 GROUP BY
     key,
     passenger_count;
-```
\ No newline at end of file
+```