spelling

docs/docs/configuration/index.md

@@ -32,7 +32,7 @@ virtual CPU. The value `0` means to spawn no threads and use the main single-thr
 
 **`default_pool_size`**
 
-Default maximum number of server connections per database pool. The pooler will not open more than this many PostgreSQL database onnections when serving clients. Default value is **`10`**.
+Default maximum number of server connections per database pool. The pooler will not open more than this many PostgreSQL database connections when serving clients. Default value is **`10`**.
 
 **`min_pool_size`**
 

docs/docs/features/healthchecks.md

@@ -1,6 +1,6 @@
 # Healthchecks
 
-Databases proxied by pgDog are regularly checked with healtchecks. A healtcheck is a simple query, e.g.
+Databases proxied by pgDog are regularly checked with healthchecks. A healthcheck is a simple query, e.g.
 `SELECT 1`, which ensures the database is reachable and able to answer requests.
 
 If a database fails a healthcheck, it's placed in a list of banned hosts. Banned databases are removed
@@ -48,7 +48,7 @@ issues, like network connectivity, to resolve themselves without manual interven
 
 ### Failsafe
 
-If all databases in a cluster are banned due to a healthcheck failure, pgDog assumes that healtchecks
+If all databases in a cluster are banned due to a healthcheck failure, pgDog assumes that Healthchecks
 are returning incorrect information and unbans all databases in the cluster. This protects against false positives
 and ensures the cluster continues to serve traffic.
 

docs/docs/features/index.md

@@ -13,7 +13,7 @@ load balancing, healthchecks, and query routing have been battle-tested and work
 |---------|-------------|-------|
 | [Transaction mode](transaction-mode.md) | Multiplex transactions and servers, allowing for high reuse of PostgreSQL server connections. | ✔️ Good |
 | [Load balancer](load-balancer.md) | Splits query traffic evenly across multiple databases. | 🔨 Work in progress |
-| [Healthcheks](healthchecks.md) | Periodically checks databases to ensure they can serve queries. | ✔️ Good |
+| [Healthchecks](healthchecks.md) | Periodically checks databases to ensure they can serve queries. | ✔️ Good |
 | [Live configuration reloading](../configuration/index.md) | Pooler configuration and users can be changed at runtime without restarting the pooler or breaking connections. | 🔨 Work in progress |
 | [Sharding](sharding/index.md) | Automatic routing of queries using a sharding key to scale writes horizontally. | 🔨 Work in progress |
 | [Plugins](plugins/index.md) | Pluggable libraries to parse and route queries, loaded at runtime. | ✔️ Good |

docs/docs/features/load-balancer.md

@@ -9,7 +9,7 @@ multiple PostgreSQL databases.
 
 ## Strategies
 
-The load balancer is configurable and can route querie
+The load balancer is configurable and can route queries
 using one of several strategies:
 
 * Random (default)

docs/docs/features/plugins/rust.md

@@ -5,7 +5,7 @@ as a bridge between plugins and pgDog internals, and provides safe methods for c
 
 ## How it works
 
-For plugins to be trully dynamic, they have to be compiled into shared libraries (`.so` on Linux, `.dylib` on Mac). This way you can load arbitrary plugins into pgDog at runtime without having to recompile it. Since Rust doesn't have a stable [ABI](https://en.wikipedia.org/wiki/Application_binary_interface), we have to use the only stable ABI available to all programming languages: C.
+For plugins to be truly dynamic, they have to be compiled into shared libraries (`.so` on Linux, `.dylib` on Mac). This way you can load arbitrary plugins into pgDog at runtime without having to recompile it. Since Rust doesn't have a stable [ABI](https://en.wikipedia.org/wiki/Application_binary_interface), we have to use the only stable ABI available to all programming languages: C.
 
 ### C ABI
 

docs/docs/features/sharding/index.md

@@ -5,7 +5,7 @@
     reflects a future state of the feature.
 
 Sharding PostgreSQL databases involves splitting the database between multiple machines and routing read
-and write queries to the correct machines using a sharding function. Like its [predecessor](https://github.com/levkk/pgcat), pgDog supports sharded PostgreSQL deployments and can route queries to the corrent shards automatically using a routing [plugin](../plugins/index.md).
+and write queries to the correct machines using a sharding function. Like its [predecessor](https://github.com/levkk/pgcat), pgDog supports sharded PostgreSQL deployments and can route queries to the correct shards automatically using a routing [plugin](../plugins/index.md).
 
 <center style="margin-top: 2rem;">
     <img src="/images/sharding.png" width="70%" alt="Sharding" />