diff --git a/docs/guides/operator/customizing-keycloak.adoc b/docs/guides/operator/customizing-keycloak.adoc index 0a324bbc90..3a64d3e5b8 100644 --- a/docs/guides/operator/customizing-keycloak.adoc +++ b/docs/guides/operator/customizing-keycloak.adoc @@ -45,7 +45,7 @@ spec: [NOTE] ==== -With custom images, every build time option passed either through a dedicated field or the `additionalOptions` is ignored. +With custom images, every build time option is passed either through a dedicated field or the `additionalOptions` is ignored. ==== diff --git a/docs/guides/server/fips.adoc b/docs/guides/server/fips.adoc index 91fe16b624..1f3605ef8d 100644 --- a/docs/guides/server/fips.adoc +++ b/docs/guides/server/fips.adoc @@ -264,7 +264,7 @@ earlier. If you prefer to avoid this option, you can for instance ask all your u == Keycloak FIPS mode on the non-fips system -Keycloak is tested on a FIPS enabled RHEL 8 system and `ubi8` image. It is supported with RHEL 9 (and `ubi9` image) as well. Running on +Keycloak is supported and tested on a FIPS enabled RHEL 8 system and `ubi8` image. It is supported with RHEL 9 (and `ubi9` image) as well. Running on the non-RHEL compatible platform or on the non-FIPS enabled platform, the FIPS compliance cannot be strictly guaranteed and cannot be officially supported. If you are still restricted to running Keycloak on such a system, you can at least update your security providers configured in `java.security` file. This update does not amount to FIPS compliance, but