docs: fix link to GitHub and small grammar fixes

docs/content/index.mdx

@@ -4,9 +4,9 @@ import { Callout } from 'nextra/components'
 
 **A collection of framework specific Cache utilities for working with <a href="https://supabase.com" alt="Supabase" target="\_parent">Supabase</a>.**
 
-> This project was initially created as part of the Supabase Launch Week 5 Hackathon and was awarded "Best Overall Project" 🥇. The official submission can be found in [hackathon.md](https://github.com/psteinroe/supabase-cache-helpers/blob/main/hackathon.md). After using it in production for 6 months, the project was rewritten, and now arrives at a stable v1.
+> This project was initially created as part of the Supabase Launch Week 5 Hackathon and was awarded "Best Overall Project" 🥇. The official submission can be found in [hackathon.md](https://github.com/psteinroe/supabase-cache-helpers/blob/main/hackathon.md). After using it in production for 6 months, the project was rewritten, and it has now arrived at a stable v1.
 
-The cache helpers bridge the gap between popular frontend cache management solutions such as [SWR](https://swr.vercel.app) or [React Query](https://tanstack.com/query/latest), and the Supabase client libraries. All features of [`postgrest-js`](https://github.com/supabase/postgrest-js), [`storage-js`](https://github.com/supabase/storage-js) and [`realtime-js`](https://github.com/supabase/realtime-js) are supported. The cache helpers parse any query into a unique and definite query key, and automatically populates your query cache with every mutation using implicit knowledge of the schema. Check out the [demo](https://supabase-cache-helpers-swr.vercel.app) and find out how it feels like for your users.
+The cache helpers bridge the gap between popular frontend cache management solutions such as [SWR](https://swr.vercel.app) or [React Query](https://tanstack.com/query/latest), and the Supabase client libraries. All features of [`postgrest-js`](https://github.com/supabase/postgrest-js), [`storage-js`](https://github.com/supabase/storage-js) and [`realtime-js`](https://github.com/supabase/realtime-js) are supported. The cache helpers parse any query into a unique and definite query key, and automatically populate your query cache with every mutation using implicit knowledge of the schema. Check out the [demo](https://supabase-cache-helpers-swr.vercel.app) and find out what it feels like for your users.
 
 <Callout emoji="✅">
   With Supabase Cache Helpers, you will never define cache keys or implement
@@ -23,14 +23,14 @@ With just one single line of code, you can simplify the logic of **fetching, sub
 - Easy **Pagination** and **Infinite Scroll** queries
 - **Insert**, **update**, **upsert** and **delete** mutations
 - **Auto-populate** cache after mutations and subscriptions
-- **Auto-expand** mutation queries based on existing cache data to keep app up-to-date
+- **Auto-expand** mutation queries based on existing cache data to keep the app up-to-date
 - One-liner to upload, download and remove **Supabase Storage** objects
 
 And a lot more.
 
 ## Motivation
 
-To maximize your velocity, you should always try to minimize the surface area of the tech. In other words, write as little code as possible.[[1]](https://paul.copplest.one/blog/nimbus-tech-2019-04.html) As apps grow, queries become more complex. At one point, you will find yourselve writing a lot of repetitive code to query data, define cache keys and update the cache after mutations. Imagine a Master-Detail view. When using SWR, you will probably end up with something like this
+To maximize your velocity, you should always try to minimize the surface area of the tech. In other words, write as little code as possible.[[1]](https://paul.copplest.one/blog/nimbus-tech-2019-04.html) As apps grow, queries become more complex. At one point, you will find yourself writing a lot of repetitive code to query data, define cache keys and update the cache after mutations. Imagine a Master-Detail view. When using SWR, you will probably end up with something like this
 
 ```ts
 const { data: posts, error } = useSWR("posts", () => {
@@ -55,11 +55,11 @@ const { data: posts, error } = useSWR("posts?is_published=true", () => {
 });
 ```
 
-You can see how this becomes very cumbersome over time. It is even more fun if you want to mutate the data, e.g. insert a new post without waiting for SWR to revalidate. To make it a smooth experience for the user, the new post should appear in the list(s) instantly, and not only after a revalidation. This can be implemented by mutating the respective cache keys. But how to know what cache keys should be mutated? One would have to decode the keys and check if the table as well as the applied filters match. Imagine doing that for large queries with a lot of filters. Not fun. But what if we could implement a generalizable solution?
+You can see how this becomes very cumbersome over time. It is even more fun if you want to mutate the data, e.g. insert a new post without waiting for SWR to revalidate. To make the user experience smooth, the new post should appear in the list(s) instantly, not only after revalidation. This can be implemented by mutating the respective cache keys. But how to know what cache keys should be mutated? One would have to decode the keys and check whether the table and the applied filters match. Imagine doing that for large queries with many filters. Not fun. But what if we could implement a generalizable solution?
 
 ## Community
 
-[![GitHub stars](https://img.shields.io/github/stars/psteinroe/supabase-cache-helpers.svg?style=social&label=Star&maxAge=2592000)](https://GitHub.com/Naereen/StrapDown.js/stargazers/)
+[![GitHub stars](https://img.shields.io/github/stars/psteinroe/supabase-cache-helpers.svg?style=social&label=Star&maxAge=2592000)](https://github.com/psteinroe/supabase-cache-helpers)
 
 Supabase Cache Helpers is created by [psteinroe](https://github.com/psteinroe).
 Follow [@psteinroe](https://twitter.com/psteinroe) on Twitter for future project updates.