From b7d8086d7fae92518eedab5d812f81b3831fdd8b Mon Sep 17 00:00:00 2001 From: zhjwpku Date: Thu, 28 Dec 2023 14:46:15 +0800 Subject: [PATCH] fix typo --- .../04-best-pratices/02-non-production-options/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/content/en/04-administration-guide/02-cluster-creation/04-best-pratices/02-non-production-options/_index.md b/doc/content/en/04-administration-guide/02-cluster-creation/04-best-pratices/02-non-production-options/_index.md index 4daf8482d0..0bcb144f18 100755 --- a/doc/content/en/04-administration-guide/02-cluster-creation/04-best-pratices/02-non-production-options/_index.md +++ b/doc/content/en/04-administration-guide/02-cluster-creation/04-best-pratices/02-non-production-options/_index.md @@ -17,7 +17,7 @@ For reference, you can see a list of all of these [non-production options]({{% r ## Scaling with limited resources -By default StackGres enforces some rules and resource requirements and limitatios in order to be production Ready by default. In case you are testing StackGres functionality it is possible to configure StackGres so that it does not prevent Pods from being scheduled in a Kubernetes cluster with insufficient resources. +By default StackGres enforces some rules and resource requirements and limitations in order to be production Ready by default. In case you are testing StackGres functionality it is possible to configure StackGres so that it does not prevent Pods from being scheduled in a Kubernetes cluster with insufficient resources. Normally StackGres requires each Pod of a Postgres cluster to be scheduled on a separate node using a Pod anti affinity rule. To disable such rule you may set the following options: