Fix typos within the text in readme file

Author: mskacelik

http-custom-mechanism/README-source.adoc

@@ -105,7 +105,7 @@ $ __{jbossHomeName}__/bin/jboss-cli.sh --connect --file=add-custom-module.cli
 
 NOTE: For Windows, use the `__{jbossHomeName}__\bin\jboss-cli.bat` script.
 
-This creates the custom `__{jbossHomeName}__/modules/modules/org/jboss/as/quickstart/http_custom_mechanism/main` folder, then copies in the `custom-module/target/custom-module.jar` file and creates the required `module.xml` file.
+This creates the custom `__{jbossHomeName}__/modules/org/jboss/as/quickstart/http_custom_mechanism/main` folder, then copies in the `custom-module/target/custom-module.jar` file and creates the required `module.xml` file.
 
 You can verify the module structure in your file manager.
 

http-custom-mechanism/README.adoc

@@ -635,7 +635,7 @@ $ __{jbossHomeName}__/bin/jboss-cli.sh --connect --file=add-custom-module.cli
 
 NOTE: For Windows, use the `__{jbossHomeName}__\bin\jboss-cli.bat` script.
 
-This creates the custom `__{jbossHomeName}__/modules/modules/org/jboss/as/quickstart/http_custom_mechanism/main` folder, then copies in the `custom-module/target/custom-module.jar` file and creates the required `module.xml` file.
+This creates the custom `__{jbossHomeName}__/modules/org/jboss/as/quickstart/http_custom_mechanism/main` folder, then copies in the `custom-module/target/custom-module.jar` file and creates the required `module.xml` file.
 
 You can verify the module structure in your file manager.
 
@@ -872,97 +872,22 @@ When you have completed testing the quickstart, you can restore the original ser
 :leveloffset!:
 
 // Additional information about this script
-This script reverts the changes made to the `undertow`  and `elytron` subsystems. You should see the following result when you run the script.
+Or you can execute the scripts provided in the root directory of this quickstart `restore-configuration.cli` to restore the original server configuration and `remove-custom-module.cli` to remove the custom module.
+[source,subs="+quotes,attributes+",options="nowrap"]
+----
+$ __{jbossHomeName}__/bin/jboss-cli.sh --connect --file=restore-configuration.cli
+$ __{jbossHomeName}__/bin/jboss-cli.sh --connect --file=remove-custom-module.cli
+----
+These scripts revert the changes made to the `undertow`  and `elytron` subsystems. You should see the following result when you run the `restore-configuration.cli` script.
 
 [source,options="nowrap"]
 ----
 The batch executed successfully
 process-state: reload-required
 ----
 
-// Restore the {productName} Standalone Server Configuration Manually
 :leveloffset: +2
 
-[[restore_standalone_server_configuration_manually]]
-= Restore the {productName} Standalone Server Configuration Manually
-//******************************************************************************
-// Include this template if your quickstart does a normal manual restoration
-// of a single standalone server.
-//******************************************************************************
-
-//******************************************************************************
-// This template sets attributes for the different standalone server profiles.
-//
-// You must define the `standalone-server-type`. Supported values are:
-//    default
-//    full
-//    full-ha
-//    ha
-//    microprofile
-//    custom
-//******************************************************************************
-
-// Standalone server with the default profile.
-ifeval::["{standalone-server-type}"=="default"]
-:serverProfile: default profile
-:configFileName: standalone/configuration/standalone.xml
-:serverArguments:
-endif::[]
-
-// Standalone server with the full profile.
-ifeval::["{standalone-server-type}"=="full"]
-:serverProfile: full profile
-:configFileName: standalone/configuration/standalone-full.xml
-:serverArguments:  -c standalone-full.xml
-endif::[]
-
-// Standalone server with the full HA profile.
-ifeval::["{standalone-server-type}"=="full-ha"]
-:serverProfile: full HA profile
-:configFileName: standalone/configuration/standalone-full-ha.xml
-:serverArguments:  -c standalone-full-ha.xml
-endif::[]
-
-// Start the standalone server with the HA profile.
-ifeval::["{standalone-server-type}"=="ha"]
-:serverProfile: HA profile
-:configFileName: standalone/configuration/standalone-ha.xml
-:serverArguments:  -c standalone-ha.xml
-endif::[]
-
-// Start the standalone server with the Eclipse MicroProfile profile.
-ifeval::["{standalone-server-type}"=="microprofile"]
-:serverProfile: MicroProfile profile
-:configFileName: standalone/configuration/standalone-microprofile.xml
-:serverArguments:  -c standalone-microprofile.xml
-endif::[]
-
-// Standalone server with the custom profile.
-// NOTE: This profile requires that you define the `serverArguments` variable
-// within the quickstart README.adoc file. For example:
-//  :serverArguments: --server-config=../../docs/examples/configs/standalone-xts.xml
-ifeval::["{standalone-server-type}"=="custom"]
-:serverProfile: custom profile
-endif::[]
-
-// If there is no match, use the default profile.
-ifndef::serverProfile[]
-:standalone-server-type:  default
-:serverProfile: default profile
-:configFileName: standalone/configuration/standalone.xml
-:serverArguments:
-endif::serverProfile[]
-
-When you have completed testing the quickstart, you can restore the original server configuration by manually restoring the backup copy the configuration file.
-
-. If it is running, stop the {productName} server.
-. Replace the `__{jbossHomeName}__/{configFileName}` file with the backup copy of the file.
-
-:leveloffset!:
-
-// Build and run sections for other environments/builds
-:leveloffset: +1
-
 [[build_and_run_the_quickstart_with_provisioned_server]]
 = Building and running the quickstart application with provisioned {productName} server