From 4f8990346b947333e1ee751228f240bc997e0c27 Mon Sep 17 00:00:00 2001 From: Evan Corkrean <62527488+corkrean@users.noreply.github.com> Date: Wed, 15 Nov 2023 12:54:49 -0700 Subject: [PATCH] feedback round 3 --- docs/spicedb-dedicated/dedicated-configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/spicedb-dedicated/dedicated-configuration.md b/docs/spicedb-dedicated/dedicated-configuration.md index 8de78b5..8e138fd 100644 --- a/docs/spicedb-dedicated/dedicated-configuration.md +++ b/docs/spicedb-dedicated/dedicated-configuration.md @@ -4,7 +4,7 @@ This guide provides information about the configuration options available to you ## Configuration Options -### Permission System Type +### Permissions System Type permissions system type @@ -20,7 +20,7 @@ Your SpiceDB Dedicated environment can be provisioned with multiple isolated [da channels config -SpiceDB Dedicated has two update channels: `rapid` and `regular` . You can select the update channel either when you launch the Permissios System or in the settings page after you’ve launched it. +SpiceDB Dedicated has two update channels: `rapid` and `regular` . You can select the update channel either when you launch the Permissions System or in the settings page after you’ve launched it. `rapid` - gets every release that is not a release candidate. @@ -36,7 +36,7 @@ After you’ve deployed your Permissions System, you can choose to keep up to da There are two rollout strategies: `rolling update` and `immediate`. -- `rolling update` is a zero downtime strategy for upgrading to a new version. This is recommended for prod permissions systems. +- `rolling update` is a zero downtime strategy for upgrading to a new version. This is recommended for prod Permissions Systems. - `immediate` involves downtime, but is faster than `rolling update`. ### Define Cluster(s)