From a0edd702fd277b39e2eb00fdd32bc3af1bd3eb25 Mon Sep 17 00:00:00 2001
From: Copple <10214025+kiwicopple@users.noreply.github.com>
Date: Thu, 13 Jul 2023 14:29:22 +0200
Subject: [PATCH] Update apps/www/_blog/2023-07-13-pgvector-performance.mdx

---
 apps/www/_blog/2023-07-13-pgvector-performance.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/www/_blog/2023-07-13-pgvector-performance.mdx b/apps/www/_blog/2023-07-13-pgvector-performance.mdx
index dea6e8fc316..69303568ccd 100644
--- a/apps/www/_blog/2023-07-13-pgvector-performance.mdx
+++ b/apps/www/_blog/2023-07-13-pgvector-performance.mdx
@@ -281,7 +281,7 @@ Before running your pgvector workload in production, here are a few steps you ca
 
 ## The pgvector roadmap
 
-pgvector is still early in development. As with any open source tool, it needs time and resources to make it better. Supabase plans to continue Andrew with his development of pgvector as much as we can.
+pgvector is still early in development. As with any open source tool, it needs time and resources to make it better. Supabase plans to continue Andrew with his development of pgvector.
 
 What's next on the roadmap? Andrew has an impressive list of features [planned for v0.5.0](https://github.com/pgvector/pgvector/issues/27):