From c7d24c33b641b4e26283aaad4e69fa93fc4a39da Mon Sep 17 00:00:00 2001
From: 0xflotus <0xflotus@gmail.com>
Date: Tue, 30 Nov 2021 23:02:40 +0100
Subject: [PATCH] Update www/_blog/2021-11-30-supabase-studio.mdx

Co-authored-by: Isaiah Hamilton <70828596+Isaiah-Hamilton@users.noreply.github.com>
---
 www/_blog/2021-11-30-supabase-studio.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/_blog/2021-11-30-supabase-studio.mdx b/www/_blog/2021-11-30-supabase-studio.mdx
index c071a8cc8c5..8440b92f640 100644
--- a/www/_blog/2021-11-30-supabase-studio.mdx
+++ b/www/_blog/2021-11-30-supabase-studio.mdx
@@ -26,7 +26,7 @@ Let's get the obvious question out of the way - why wasn't it already open sourc
 When Ant and I started Supabase the codebase was one large monorepo which contained everything from the dashboard to cloud infrastructure code to experimental code. 
 This is our preferred development setup - we like to keep all code in one place so that we have a single source of truth and tightly coupled CI workflows.
 
-The original Dashboard really wasn't much except a couple of button which allowed our Alpha users to start and stop a Supabase project - back then only a PostgreSQL connection string.
+The original Dashboard really wasn't much except a couple of buttons which allowed our Alpha users to start and stop a Supabase project - back then only a PostgreSQL connection string.
 
 Then time went on, and we started gaining traction - a lot faster than expected. 
 The nice thing about building for developers is that they are very vocal about the features they want to see next.