- replace "will be deployed" with "is deployed" under pki/docs/instal…

…lation

- remove backticks surrounding words (instead of names) under pki/docs/installation
- remove the extra ", for example" under pki/docs/installation
[skip ci]

docs/installation/ca/Installing_CA.adoc

@@ -7,7 +7,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 == CA Subsystem Installation 
 
 Prepare a deployment configuration, for example `ca.cfg`, to deploy CA subsystem.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/ca.cfg[/usr/share/pki/server/examples/installation/ca.cfg].
 

docs/installation/ca/Installing_CA_Clone.adoc

@@ -30,7 +30,7 @@ The command will export the following certificates (including the certificate ch
 
 Note that the existing SSL server certificate will not be exported.
 
-If necessary, third-party certificates, for example `trust anchors`, can be added into the same PKCS #12 file with the following command:
+If necessary, third-party certificates, for example trust anchors, can be added into the same PKCS #12 file with the following command:
 
 [literal,subs="+quotes,verbatim"]
 ....
@@ -76,7 +76,7 @@ $ chown pkiuser:pkiuser ca-certs.p12
 == CA Subsystem Installation 
 
 Prepare a deployment configuration, for example `ca-clone.cfg`, to deploy CA subsystem clone.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/ca-clone.cfg[/usr/share/pki/server/examples/installation/ca-clone.cfg].
 It assumes that the primary CA subsystem is running at https://primary.example.com:8443,

docs/installation/ca/Installing_CA_Clone_with_HSM.adoc

@@ -33,7 +33,7 @@ $ pki-server cert-export subsystem \
 
 Note: It is assumed that the CA signing certificate has been exported into `ca_signing.crt`
 
-Prepare a file, for example `ca.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `ca.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ca/Installing_CA_Clone_with_Secure_Database_Connection.adoc

@@ -57,9 +57,9 @@ The command will export the following certificates (including the certificate ch
 * audit signing certificate
 * subsystem certificate
 
-Note that the existing SSL server certificate will not be exported.
+Note that the existing SSL server certificate is not exported.
 
-If necessary, third-party certificates, for example `trust anchors`, can be added into the same PKCS #12 file with the following command:
+If necessary, third-party certificates, for example trust anchors, can be added into the same PKCS #12 file with the following command:
 
 [literal,subs="+quotes,verbatim"]
 ....
@@ -88,7 +88,7 @@ $ chown pkiuser:pkiuser ca-certs.p12
 == CA Subsystem Installation 
 
 Prepare a deployment configuration, for example `ca-secure-ds-secondary.cfg`, to deploy CA subsystem clone.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/ca-secure-ds-secondary.cfg[/usr/share/pki/server/examples/installation/ca-secure-ds-secondary.cfg].
 It assumes that the existing CA and DS instances are running on primary.example.com, and the new CA and DS clones are being installed on secondary.example.com,

docs/installation/ca/Installing_CA_with_Custom_CA_Signing_Key.adoc

@@ -5,7 +5,7 @@ Follow this process to install a CA subsystem with a custom CA signing key, CSR,
 Prior to installation, please ensure that the link:../others/Installation_Prerequisites.adoc[Installation Prerequisites] are configured.
 
 == Starting CA Subsystem Installation 
-Prepare a file, for example `ca-step1.cfg`, that contains the deployment configuration step 1, for example:
+Prepare a file, for example `ca-step1.cfg`, that contains the deployment configuration step 1:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ca/Installing_CA_with_ECC.adoc

@@ -19,7 +19,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 == CA Subsystem Installation 
 
 Prepare a deployment configuration, for example `ca-ecc.cfg`, to deploy CA subsystem.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/ca-ecc.cfg[/usr/share/pki/server/examples/installation/ca-ecc.cfg].
 

docs/installation/ca/Installing_CA_with_Existing_Keys_in_HSM.adoc

@@ -9,7 +9,7 @@ so they will not be included in the installation process.
 Prior to installation, please ensure that the link:../others/Installation_Prerequisites.adoc[Installation Prerequisites] are configured.
 
 == Starting CA Subsystem Installation 
-Prepare a file, for example `ca-step1.cfg`, that contains the deployment configuration step 1, for example:
+Prepare a file, for example `ca-step1.cfg`, that contains the deployment configuration step 1:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ca/Installing_CA_with_HSM.adoc

@@ -6,7 +6,7 @@ where the system certificates and their keys will be stored in HSM.
 Prior to installation, please ensure that the link:../others/Installation_Prerequisites.adoc[Installation Prerequisites] are configured.
 
 == CA Subsystem Installation 
-Prepare a file, for example `ca.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `ca.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ca/Installing_CA_with_Secure_Database_Connection.adoc

@@ -12,7 +12,7 @@ link:../others/Exporting-DS-Certificates.adoc#exporting-ds-signing-certificate[E
 
 == CA Subsystem Installation 
 Prepare a deployment configuration, for example `ca-secure-ds.cfg`, to deploy CA subsystem.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/ca-secure-ds.cfg[/usr/share/pki/server/examples/installation/ca-secure-ds.cfg].
 

docs/installation/kra/Installing_KRA_Clone.adoc

@@ -25,7 +25,7 @@ The command will export the following certificates (including the certificate ch
 
 Note that the existing SSL server certificate will not be exported.
 
-If necessary, third-party certificates, for example `trust anchors`, can be added into the same PKCS #12 file with the following command:
+If necessary, third-party certificates, for example trust anchors, can be added into the same PKCS #12 file with the following command:
 
 [literal,subs="+quotes,verbatim"]
 ....
@@ -39,7 +39,7 @@ $ pki -d /var/lib/pki/pki-tomcat/conf/alias -f /var/lib/pki/pki-tomcat/conf/pass
 == KRA Subsystem Installation 
 
 Prepare a deployment configuration, for example `kra-clone.cfg`, to deploy KRA subsystem clone.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/kra-clone.cfg[/usr/share/pki/server/examples/installation/kra-clone.cfg].
 It assumes that the primary CA and KRA subsystems are running at https://primary.example.com:8443,

docs/installation/kra/Installing_KRA_Clone_with_HSM.adoc

@@ -13,7 +13,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 Note: It is assumed that the CA signing certificate has been exported into `ca_signing.crt`
 
-Prepare a file, for example `kra.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `kra.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/kra/Installing_KRA_with_Custom_Keys.adoc

@@ -7,7 +7,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == Starting KRA Subsystem Installation
 
-Prepare a file, for example `kra-step1.cfg`, that contains the deployment configuration step 1, for example:
+Prepare a file, for example `kra-step1.cfg`, that contains the deployment configuration step 1:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/kra/Installing_KRA_with_ECC.adoc

@@ -19,7 +19,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == KRA Subsystem Installation
 
-Prepare a file, for example `kra.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `kra.cfg`, that contains the deployment configuration:
 [literal,subs="+quotes,verbatim"]
 ....
 [DEFAULT]

docs/installation/kra/Installing_KRA_with_HSM.adoc

@@ -8,7 +8,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == KRA Subsystem Installation
 
-Prepare a file, for example `kra.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `kra.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/kra/Installing_KRA_with_Secure_Database_Connection.adoc

@@ -9,7 +9,7 @@ This step is described link:https://www.dogtagpki.org/wiki/DS_SSL[here].
 
 == KRA Subsystem Installation
 
-Prepare a file, for example `kra.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `kra.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ocsp/Installing_OCSP_Clone.adoc

@@ -24,7 +24,7 @@ The command will export the following certificates (including the certificate ch
 
 Note that the existing SSL server certificate will not be exported.
 
-If necessary, third-party certificates, for example `trust anchors`, can be added into the same PKCS #12 file with the following command:
+If necessary, third-party certificates, for example trust anchors, can be added into the same PKCS #12 file with the following command:
 
 [literal,subs="+quotes,verbatim"]
 ....
@@ -38,7 +38,7 @@ $ pki -d /var/lib/pki/pki-tomcat/conf/alias -f /var/lib/pki/pki-tomcat/conf/pass
 == OCSP Subsystem Installation 
 
 Prepare a deployment configuration, for example `ocsp-clone.cfg`, to deploy OCSP subsystem clone.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/ocsp-clone.cfg[/usr/share/pki/server/examples/installation/ocsp-clone.cfg].
 It assumes that the primary CA and OCSP subsystems are running at https://primary.example.com:8443,

docs/installation/ocsp/Installing_OCSP_Clone_with_HSM.adoc

@@ -14,7 +14,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 Note: It is assumed that the CA signing certificate has been exported into `ca_signing.crt
 
-Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ocsp/Installing_OCSP_with_Custom_Keys.adoc

@@ -8,7 +8,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == Starting OCSP Subsystem Installation 
 
-Prepare a file, for example `ocsp-step1.cfg`, that contains the deployment configuration step 1, for example:
+Prepare a file, for example `ocsp-step1.cfg`, that contains the deployment configuration step 1:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ocsp/Installing_OCSP_with_ECC.adoc

@@ -19,7 +19,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == OCSP Subsystem Installation 
 
-Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ocsp/Installing_OCSP_with_HSM.adoc

@@ -7,7 +7,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == OCSP Subsystem Installation 
 
-Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/ocsp/Installing_OCSP_with_Secure_Database_Connection.adoc

@@ -11,7 +11,7 @@ Ensure that the secure connection has been enabled on the directory server, and
 
 == OCSP Subsystem Installation 
 
-Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `ocsp.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/server/Installing_Basic_PKI_Server.adoc

@@ -2,7 +2,7 @@
 
 
 Follow this process to create and configure a basic PKI server without any of the PKI subsystems.
-This would be useful to troubleshoot general server issues, for example `SSL`.
+This would be useful to troubleshoot general server issues, for example SSL.
 
 == Installation
 

docs/installation/server/Installing_PKI_Server_with_Custom_NSS_Databases.adoc

@@ -3,12 +3,12 @@
 
 Follow this process to create a PKI server with custom NSS databases.
 
-Normally, when installing a PKI subsystem, for example `CA`, some NSS databases will be created by default, for example:
+Normally, when installing a PKI subsystem, for example CA, some NSS databases will be created by default:
 
 * server NSS database: /var/lib/pki/pki-tomcat/conf/alias
 * admin NSS database: ~/.dogtag/pki-tomcat/ca/alias
 
-Under some circumstances the admin may want to use custom NSS databases, for example `with trust policy`.
+Under some circumstances the admin may want to use custom NSS databases, for example with trust policy.
 In those cases the installation can be done in multiple steps:
 
 * create a basic PKI server

docs/installation/tks/Installing_TKS_Clone.adoc

@@ -23,7 +23,7 @@ The command will export the following certificates (including the certificate ch
 
 Note that the existing SSL server certificate will not be exported.
 
-If necessary, third-party certificates, for example `trust anchors`, can be added into the same PKCS #12 file with the following command:
+If necessary, third-party certificates, for example trust anchors, can be added into the same PKCS #12 file with the following command:
 
 [literal,subs="+quotes,verbatim"]
 ....
@@ -37,7 +37,7 @@ $ pki -d /var/lib/pki/pki-tomcat/conf/alias -f /var/lib/pki/pki-tomcat/conf/pass
 == TKS Subsystem Installation
 
 Prepare a deployment configuration, for example `tks-clone.cfg`, to deploy TKS subsystem clone.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/tks-clone.cfg[/usr/share/pki/server/examples/installation/tks-clone.cfg].
 It assumes that the primary CA and TKS are running at https://primary.example.com:8443,

docs/installation/tks/Installing_TKS_with_ECC.adoc

@@ -19,7 +19,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == TKS Subsystem Installation
 
-Prepare a file, for example `tks.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `tks.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/tks/Installing_TKS_with_HSM.adoc

@@ -8,7 +8,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == TKS Subsystem Installation
 
-Prepare a file, for example `tks.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `tks.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/tks/Installing_TKS_with_Secure_Database_Connection.adoc

@@ -9,7 +9,7 @@ This step is described link:https://www.dogtagpki.org/wiki/DS_SSL[here].
 
 == TKS Subsystem Installation
 
-Prepare a file, for example `tks.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `tks.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/tps/Installing_TPS_Clone.adoc

@@ -24,7 +24,7 @@ The command will export the following certificates (including the certificate ch
 
 Note that the existing SSL server certificate will not be exported.
 
-If necessary, third-party certificates, for example `trust anchors`, can be added into the same PKCS #12 file with the following command:
+If necessary, third-party certificates, for example trust anchors, can be added into the same PKCS #12 file with the following command:
 
 [literal,subs="+quotes,verbatim"]
 ....
@@ -38,7 +38,7 @@ $ pki -d /var/lib/pki/pki-tomcat/conf/alias -f /var/lib/pki/pki-tomcat/conf/pass
 == TPS Subsystem Installation
 
 Prepare a deployment configuration, for example `tps-clone.cfg`, to deploy TPS subsystem clone.
-By default the subsystem will be deployed into a Tomcat instance called `pki-tomcat`.
+By default the subsystem is deployed into a Tomcat instance called `pki-tomcat`.
 
 A sample deployment configuration is available at link:../../../base/server/examples/installation/tps-clone.cfg[/usr/share/pki/server/examples/installation/tps-clone.cfg].
 It assumes that the primary CA, KRA, TKS, and TPS subsystems are running at https://primary.example.com:8443,

docs/installation/tps/Installing_TPS_with_HSM.adoc

@@ -8,7 +8,7 @@ Prior to installation, please ensure that the link:../others/Installation_Prereq
 
 == TPS Subsystem Installation
 
-Prepare a file, for example `tps.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `tps.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....

docs/installation/tps/Installing_TPS_with_Secure_Database_Connection.adoc

@@ -9,7 +9,7 @@ This step is described link:https://www.dogtagpki.org/wiki/DS_SSL[here].
 
 == TPS Subsystem Installation
 
-Prepare a file, for example `tps.cfg`, that contains the deployment configuration, for example:
+Prepare a file, for example `tps.cfg`, that contains the deployment configuration:
 
 [literal,subs="+quotes,verbatim"]
 ....