Skip to content

Open-source status page, incident response and uptime monitoring

Grammar Polishing (#422)

Diogo Ribeirod0a37728080d
diff --git a/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx b/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx
index 6dba04cb0..90fa41000 100644
--- a/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx
+++ b/apps/web/src/content/posts/migration-backend-from-vercel-to-fly.mdx
@@ -11,11 +11,11 @@ publishedAt: 2023-10-29
image: /assets/posts/migration-backend-from-vercel-to-fly/fly-dashboard.png
---
-In this article we are going to see the reason that made us change our backend
+In this article, we are going to see the reasons that made us change our backend
to Fly.io and the challenges we had during the migrations.
We chose [Hono](https://hono.dev/) as our API server with [Bun](https://bun.sh/)
-as the runtime and pick Fly.io as your hosting service.
+as the runtime and picked Fly.io as our hosting service.
## 🤔 Why did we want to move our backend from Vercel?