Fix typo

Signed-off-by: Nicolas Bigler <nicolas.bigler@vshn.ch>
vshn · Aug 9, 2024 · 2e558d5 · 2e558d5
1 parent 4b09ea3
commit 2e558d5
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/docs/modules/ROOT/pages/vshn-managed/keycloak/security.adoc b/docs/modules/ROOT/pages/vshn-managed/keycloak/security.adoc
@@ -31,7 +31,7 @@ On APPUiO Cloud, every member of the same organization to which the claim namesp
 
 On APPUiO Managed, we don't have this construct and no RBAC rules are deployed by default.
 
-However, it is possible to specify a list of `Groups` or `Users`that should have that limited access to the namespace.
+However, it is possible to specify a list of `Groups` or `Users` that should have that limited access to the namespace.
 This can be done using the two fields `allowedGroups` and `allowedUsers`:
 
 [source,yaml]

diff --git a/docs/modules/ROOT/pages/vshn-managed/mariadb/security.adoc b/docs/modules/ROOT/pages/vshn-managed/mariadb/security.adoc
@@ -31,7 +31,7 @@ On APPUiO Cloud, every member of the same organization to which the claim namesp
 
 On APPUiO Managed, we don't have this construct and no RBAC rules are deployed by default.
 
-However, it is possible to specify a list of `Groups` or `Users`that should have that limited access to the namespace.
+However, it is possible to specify a list of `Groups` or `Users` that should have that limited access to the namespace.
 This can be done using the two fields `allowedGroups` and `allowedUsers`:
 
 [source,yaml]

diff --git a/docs/modules/ROOT/pages/vshn-managed/nextcloud/security.adoc b/docs/modules/ROOT/pages/vshn-managed/nextcloud/security.adoc
@@ -31,7 +31,7 @@ On APPUiO Cloud, every member of the same organization to which the claim namesp
 
 On APPUiO Managed, we don't have this construct and no RBAC rules are deployed by default.
 
-However, it is possible to specify a list of `Groups` or `Users`that should have that limited access to the namespace.
+However, it is possible to specify a list of `Groups` or `Users` that should have that limited access to the namespace.
 This can be done using the two fields `allowedGroups` and `allowedUsers`:
 
 [source,yaml]

diff --git a/docs/modules/ROOT/pages/vshn-managed/postgresql/security.adoc b/docs/modules/ROOT/pages/vshn-managed/postgresql/security.adoc
@@ -31,7 +31,7 @@ On APPUiO Cloud, every member of the same organization to which the claim namesp
 
 On APPUiO Managed, we don't have this construct and no RBAC rules are deployed by default.
 
-However, it is possible to specify a list of `Groups` or `Users`that should have that limited access to the namespace.
+However, it is possible to specify a list of `Groups` or `Users` that should have that limited access to the namespace.
 This can be done using the two fields `allowedGroups` and `allowedUsers`:
 
 [source,yaml]

diff --git a/docs/modules/ROOT/pages/vshn-managed/redis/security.adoc b/docs/modules/ROOT/pages/vshn-managed/redis/security.adoc
@@ -31,7 +31,7 @@ On APPUiO Cloud, every member of the same organization to which the claim namesp
 
 On APPUiO Managed, we don't have this construct and no RBAC rules are deployed by default.
 
-However, it is possible to specify a list of `Groups` or `Users`that should have that limited access to the namespace.
+However, it is possible to specify a list of `Groups` or `Users` that should have that limited access to the namespace.
 This can be done using the two fields `allowedGroups` and `allowedUsers`:
 
 [source,yaml]