From d2f4196146137238a44340d6e7bb7018e88ce1c1 Mon Sep 17 00:00:00 2001 From: Nabeel Sulieman Date: Wed, 15 Feb 2023 11:48:30 -0800 Subject: [PATCH] docs(overview): Grammar/Language Tweaks (#5159) Minor grammar/language update Suggestions to improve the readability/flow of the Production Setup section. Co-authored-by: Florian Forster --- docs/docs/self-hosting/deploy/overview.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/self-hosting/deploy/overview.mdx b/docs/docs/self-hosting/deploy/overview.mdx index e9bd80b0c..c9acfa57a 100644 --- a/docs/docs/self-hosting/deploy/overview.mdx +++ b/docs/docs/self-hosting/deploy/overview.mdx @@ -25,9 +25,9 @@ The easiest way to use ZITADEL is to run one of our container releases # Production Setup -As soon as you successfully created your first test environment using one of the deployment guides in this section, +After you have successfully created your first test environment using one of the deployment guides in this section, you might want to configure ZITADEL for production and embed it into your system landscape. To do so, jump straight to the [production setup guide](/docs/self-hosting/manage/production). -To achieving high availability, we recommend to use a [Kubernetes](https://kubernetes.io/docs/home/) Cluster. +To achieve high availability, we recommend using a [Kubernetes](https://kubernetes.io/docs/home/) Cluster. We have an official [Helm chart](https://artifacthub.io/packages/helm/zitadel/zitadel) for easy deployment and maintenance.