summaryrefslogtreecommitdiff
path: root/doc/development/scalability.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/scalability.md')
-rw-r--r--doc/development/scalability.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/scalability.md b/doc/development/scalability.md
index d4772bf3ea5..37ffdbdbfde 100644
--- a/doc/development/scalability.md
+++ b/doc/development/scalability.md
@@ -165,7 +165,7 @@ and secondaries are set up a bit differently:
For replicas, colocating is advantageous because it reduces network hops
and hence latency. However, for the primary, colocating is
disadvantageous because PgBouncer would become a single point of failure
-and cause errors. When a failover occurs, one of two things could
+and cause errors. When a failover occurs, one of two things could
happen:
- The primary disappears from the network.
@@ -212,7 +212,7 @@ Redis process.
#### High availability/Risks
Single-core: Like PgBouncer, a single Redis process can only use one
-core. It does not support multi-threading.
+core. It does not support multi-threading.
Dumb secondaries: Redis secondaries (aka slaves) don't actually
handle any load. Unlike PostgreSQL secondaries, they don't even serve