diff --git a/securing_apps/topics/oidc/java/jboss-adapter-rpms.adoc b/securing_apps/topics/oidc/java/jboss-adapter-rpms.adoc
index 7ec5f21caf..c4f0a7e334 100644
--- a/securing_apps/topics/oidc/java/jboss-adapter-rpms.adoc
+++ b/securing_apps/topics/oidc/java/jboss-adapter-rpms.adoc
@@ -33,7 +33,7 @@ Install the {appserver_name} 7 adapters for OIDC using the following command at
 $ sudo yum install eap7-keycloak-adapter-sso7_3
 ----
 
-or use following one for Red Hat Red Hat Enterprise Linux 8:
+or use following one for Red Hat Enterprise Linux 8:
 
 ----
 $ sudo dnf install eap7-keycloak-adapter-sso7_3
diff --git a/securing_apps/topics/saml/java/jboss-adapter/jboss-adapter-rpms.adoc b/securing_apps/topics/saml/java/jboss-adapter/jboss-adapter-rpms.adoc
index 247f43ea93..4dab8761fd 100644
--- a/securing_apps/topics/saml/java/jboss-adapter/jboss-adapter-rpms.adoc
+++ b/securing_apps/topics/saml/java/jboss-adapter/jboss-adapter-rpms.adoc
@@ -33,7 +33,7 @@ Install the EAP 7 adapters for SAML using the following command:
 $ sudo yum install eap7-keycloak-saml-adapter-sso7_3
 ----
 
-or use following one for Red Hat Red Hat Enterprise Linux 8:
+or use following one for Red Hat Enterprise Linux 8:
 
 ----
 $ sudo dnf install eap7-keycloak-adapter-sso7_3
diff --git a/server_admin/topics/authentication/x509.adoc b/server_admin/topics/authentication/x509.adoc
index b2e397b4cf..3a6e58f285 100644
--- a/server_admin/topics/authentication/x509.adoc
+++ b/server_admin/topics/authentication/x509.adoc
@@ -172,7 +172,7 @@ Defines how to extract the user identity from a client certificate.
 Defines whether to use the canonical format to determine a distinguished name.
 The format is described in detail in the official link:https://docs.oracle.com/javase/8/docs/api/javax/security/auth/x500/X500Principal.html#getName-java.lang.String-[Java API documentation] .
 This option only affects the two User Identity Sources _Match SubjectDN using regular expression_ and _Match IssuerDN using regular expression_.
-If you setup a new keycloak instance it is recommended to enable this option. Leave this option disabled to remain beckward compatible with existing Keycloak instances.
+If you setup a new {project_name} instance it is recommended to enable this option. Leave this option disabled to remain beckward compatible with existing {project_name} instances.
 
 `Enable Serial Number hexadecimal representation` (optional)::
 An option to use hexadecimal representation of the Serial Number. See link:https://tools.ietf.org/html/rfc5280#section-4.1.2.2[RFC5280, Section-4.1.2.2]. Serial Number with sign bit set to 1 should be left padded with 00 octet. E.g. Serial number with decimal value _161_, or _a1_ in hexadecimal representation according to RFC5280 must be encoded as _00a1_. More details can be found: link:https://tools.ietf.org/html/rfc5280#appendix-B[RFC5280, appendix-B].
diff --git a/server_admin/topics/clients/client-oidc.adoc b/server_admin/topics/clients/client-oidc.adoc
index e9eae56f34..a7a4c564cd 100644
--- a/server_admin/topics/clients/client-oidc.adoc
+++ b/server_admin/topics/clients/client-oidc.adoc
@@ -157,7 +157,7 @@ The administrator can select the following three options:
 
 *Proof Key for Code Exchange Code Challenge Method*
 
-* (blank) : {project_name} does not apply PKCE unless the client sends PKCE's parameters appropriately to keycloak's authorization endpoint. It is the default setting.
+* (blank) : {project_name} does not apply PKCE unless the client sends PKCE's parameters appropriately to {project_name}'s authorization endpoint. It is the default setting.
 * S256 : {project_name} applies to the client PKCE whose code challenge method is S256.
 * plain : {project_name} applies to the client PKCE whose code challenge method is plain.