From e85f0cef0057b1b6a07d3aa6bb99b86e1a9f89fb Mon Sep 17 00:00:00 2001 From: Aboullos <61687012+Aboullos@users.noreply.github.com> Date: Wed, 25 Mar 2020 11:49:10 +0100 Subject: [PATCH] KEYCLOAK-13447 Typo in domain.adoc --- server_installation/topics/operating-mode/domain.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/server_installation/topics/operating-mode/domain.adoc b/server_installation/topics/operating-mode/domain.adoc index 8e3a9e680e..73f8880f81 100644 --- a/server_installation/topics/operating-mode/domain.adoc +++ b/server_installation/topics/operating-mode/domain.adoc @@ -5,7 +5,7 @@ Domain mode is a way to centrally manage and publish the configuration for your servers. Running a cluster in standard mode can quickly become aggravating as the cluster grows in size. Every time you need -to make a configuration change, you have perform it on each node in the cluster. Domain mode solves this problem by providing +to make a configuration change, you have to perform it on each node in the cluster. Domain mode solves this problem by providing a central place to store and publish configuration. It can be quite complex to set up, but it is worth it in the end. This capability is built into the {appserver_name} Application Server which {project_name} derives from. @@ -198,7 +198,7 @@ $ .../bin/domain.sh --host-config=host-master.xml > ...\bin\domain.bat --host-config=host-master.xml ---- -When running the boot script you will need pass in the host controlling configuration file you are going to use via the +When running the boot script you will need to pass in the host controlling configuration file you are going to use via the `--host-config` switch. [[_clustered-domain-example]]