From b049d52a56e71250cd9dc6a67a28a52fd1440444 Mon Sep 17 00:00:00 2001 From: Copple <10214025+kiwicopple@users.noreply.github.com> Date: Thu, 16 Feb 2023 20:22:05 +0100 Subject: [PATCH] Update apps/www/_blog/2023-02-16-case-study-happyteams.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- apps/www/_blog/2023-02-16-case-study-happyteams.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2023-02-16-case-study-happyteams.mdx b/apps/www/_blog/2023-02-16-case-study-happyteams.mdx index f9bfd2427ed..c0aa8d5d4db 100644 --- a/apps/www/_blog/2023-02-16-case-study-happyteams.mdx +++ b/apps/www/_blog/2023-02-16-case-study-happyteams.mdx @@ -35,7 +35,7 @@ There were four main factors that led HappyTeams to switch from Heroku Postgres 4. **Lower costs**. Moving to Supabase reduced HappyTeams's costs: The base plan comes with everything they need to scale the product. -Great documentation, great product, great pricing. It sells itself, really. + Great documentation, great product, great pricing. It sells itself, really. ## Supabase provides a fast and reliable production database