docs: grammar & punctuation fixes (#8)

* docs(faq): add missing preposition

* docs(philosophy): grammar & punctuation fixes

Signed-off-by: Vladislav Doster <[email protected]>

---------

Signed-off-by: Vladislav Doster <[email protected]>

Author: vladdoster

docs/src/content/docs/getting-started/philosophy.mdx

@@ -18,12 +18,12 @@ carefully picking the right components for doing the heavy lifting.
 ### _Simplicity_
 
 To avoid demoting _simplicity_ to just another popular marketing term, let's
-start by clarify what we mean.
+start by clarifying what we mean.
 Simplicity is a relative property in the context of a problem:
 a simple solution for a simple problem is straightforward to understand,
 validate, extend or even replace.
 A simple solution solution for a hard problem will naturally be more involved
-but retains above properties within a more complex context.
+but retains the above properties within a more complex context.
 
 "Simple" is different from "easy".
 An easy solution may be very complex in an effort to take on as much
@@ -50,8 +50,8 @@ For example and tying back to TrailBase:
 
 The way we defined _simplicity_ above, loose coupling is already an important
 property of a good-natured, simple solution. Yet, we believe it's a critical
-property in its own right that should be called out explicitly helping to
-illustrate the guiding principles underpinning TrailBase.
+property in its own right that should be called out explicitly to
+help illustrate the guiding principles underpinning TrailBase.
 Looking at two examples:
 
 __Admin Dashboard__: TrailBase offers an easy-to-use, integrated admin dashboard.
@@ -68,10 +68,10 @@ ORMs often yield simple looking examples but then fall flat soon after going
 beyond the tutorial, sometimes already when joining tables.
 Your data model should never be driven by the short-comings of an abstraction
 forced upon you.
-ORMs aren't without merit. Often they will provide type-safe APIs for accessing
+ORMs aren't without merit. Often, they provide type-safe APIs for accessing
 the database. While more constraint, TrailBase's end-to-end type-safety
 provides similar benefits.
-Leaning into HTTP, JSON and JSON schema to makes it easy for TrailBase to
+Leaning into HTTP, JSON and JSON schema makes it easy for TrailBase to
 provide consistent cross-language client-side type-safety [^1], giving you more
 freedom in choosing the right tool for a specific job.
 

docs/src/content/docs/reference/faq.mdx

@@ -48,7 +48,7 @@ solutions but you probably will be fine 😶‍🌫️ .
 Long answer: TrailBase currently only scales vertically, however it's incredibly
 fast. Besides, there's an inherent beauty to vertical scaling [^1] and modern
 servers can get you very very far.
-You can absolutely support tens of thousands or even hundreds thousands of
+You can absolutely support tens of thousands or even hundreds of thousands of
 concurrent users with a single database.
 With TrailBase simple deployment, it may also be an option to shard your users
 or tenants across multiple databases. In the future, TrailBase would also like