Replace callouts in LB guide with alternative wording (#4278)

(cherry picked from commit 3dee2a2)

Author: aneta-petrova

guides/common/modules/proc_creating-a-custom-ssl-certificate.adoc

@@ -71,22 +71,29 @@ x509_extensions = usr_cert
 prompt = no
 
 [ req_distinguished_name ]
-commonName = _{ssl-common-name}_ <1>
+commonName = _{ssl-common-name}_
 
 [ v3_req ]
 basicConstraints = CA:FALSE
 keyUsage = digitalSignature, keyEncipherment
 extendedKeyUsage = serverAuth, clientAuth
 subjectAltName = @alt_names
 
-[alt_names] <2>
+[alt_names]
 DNS.1 = _{loadbalancer-example-com}_
 DNS.2 = _{smartproxy-example-com}_
 ----
-<1> The certificate's common name must match the FQDN of {SmartProxyServer}.
++
+The options used in the configuration file include the following:
++
+`commonName`::
+The certificate common name.
+It must match the FQDN of {SmartProxyServer}.
 Ensure to change this when running the command on each {SmartProxyServer} that you configure for load balancing.
 You can also set a wildcard value `*`.
-<2> Under `[alt_names]`, include the FQDN of the load balancer as `DNS.1` and the FQDN of {SmartProxyServer} as `DNS.2`.
+`[alt_names]`::
+The alternative names for the load balancer and {SmartProxyServer}.
+Include the FQDN of the load balancer as `DNS.1` and the FQDN of {SmartProxyServer} as `DNS.2`.
 endif::[]
 +
 For more information about the `[ v3_req ]` parameters and their purpose, see link:https://www.rfc-editor.org/rfc/rfc5280[RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile].
@@ -96,28 +103,41 @@ For more information about the `[ v3_req ]` parameters and their purpose, see li
 ----
 [req_distinguished_name]
 CN = _{ssl-common-name}_
-countryName = _My_Country_Name_ <1>
-stateOrProvinceName = _My_State_Or_Province_Name_ <2>
-localityName = _My_Locality_Name_ <3>
+countryName = _My_Country_Name_
+stateOrProvinceName = _My_State_Or_Province_Name_
+localityName = _My_Locality_Name_
 organizationName = _My_Organization_Or_Company_Name_
-organizationalUnitName = _My_Organizational_Unit_Name_ <4>
+organizationalUnitName = _My_Organizational_Unit_Name_
 ----
-<1> Two letter code
-<2> Full name
-<3> Full name (example: New York)
-<4> Division responsible for the certificate (example: IT department)
++
+The options used in the configuration file include the following:
++
+`countryName`::
+The country represented by a two-letter code
+`stateOrProvinceName`::
+Full name of the state or province
+`localityName`::
+Full name of the locality (example: New York)
+`organizationalUnitName`::
+Division responsible for the certificate (example: IT department)
 . Generate CSR:
 +
 [options="nowrap", subs="+quotes,attributes"]
 ----
 # openssl req -new \
--key _/root/{cert-name}_cert/{cert-name}_cert_key.pem_ \ <1>
--config _/root/{cert-name}_cert/openssl.cnf_ \ <2>
--out _/root/{cert-name}_cert/{cert-name}_cert_csr.pem_ <3>
+-key _/root/{cert-name}_cert/{cert-name}_cert_key.pem_ \
+-config _/root/{cert-name}_cert/openssl.cnf_ \
+-out _/root/{cert-name}_cert/{cert-name}_cert_csr.pem_
 ----
-<1> Path to the private key
-<2> Path to the configuration file
-<3> Path to the CSR to generate
++
+The options used in the configuration file include the following:
++
+`-key`::
+Path to the private key
+`-config`::
+Path to the configuration file
+`-out`::
+Path to the CSR to generate
 . Send the certificate signing request to the certificate authority (CA).
 The same CA must sign certificates for {ProjectServer} and {SmartProxyServer}.
 +

guides/common/modules/proc_registering-clients-using-the-bootstrap-script.adoc

@@ -18,18 +18,24 @@ For more information, see {ManagingHostsDocURL}Registering_Hosts_by_Using_the_Bo
 ----
 # /usr/libexec/platform-python bootstrap.py \
 --activationkey="_My_Activation_Key_" \
---enablerepos={project-client-RHEL8-url} \ <1>
---force \ <2>
+--enablerepos={project-client-RHEL8-url} \
+--force \
 --hostgroup="_My_Host_Group_" \
 --location="_My_Location_" \
 --login=_admin_ \
 --organization="_My_Organization_" \
---puppet-ca-port 8141 \ <3>
+--puppet-ca-port 8141 \
 --server _{loadbalancer-example-com}_
 ----
-<1> Replace `<arch>` with the client architecture, for example `x86`.
-<2> Include the `--force` option to register the client that has been previously registered to a standalone {SmartProxy}.
-<3> Include the `--puppet-ca-port 8141` option if you use Puppet.
++
+The options used in the command include the following:
++
+`enablerepos`::
+Replace `<arch>` with the client architecture, for example `x86`.
+`--force`::
+Include the `--force` option to register the client that has been previously registered to a standalone {SmartProxy}.
+`--puppet-ca-port`::
+Include the `--puppet-ca-port 8141` option if you use Puppet.
 
 * On {EL} 7, enter the following command:
 +
@@ -38,14 +44,19 @@ For more information, see {ManagingHostsDocURL}Registering_Hosts_by_Using_the_Bo
 # python bootstrap.py --login=_admin_ \
 --activationkey="_My_Activation_Key_" \
 --enablerepos={project-client-RHEL7-url} \
---force \ <1>
+--force \
 --hostgroup="_My_Host_Group_" \
 --location="_My_Location_" \
 --organization="_My_Organization_" \
---puppet-ca-port 8141 \ <2>
+--puppet-ca-port 8141 \
 --server _{loadbalancer-example-com}_
 ----
-<1> Include the `--force` option to register the client that has been previously registered to a standalone {SmartProxy}.
-<2> Include the `--puppet-ca-port 8141` option if you use Puppet.
++
+The options used in the command include the following:
++
+`--force`::
+Include the `--force` option to register the client that has been previously registered to a standalone {SmartProxy}.
+`--puppet-ca-port`::
+Include the `--puppet-ca-port 8141` option if you use Puppet.
 +
 The script prompts for the password corresponding to the {Project} user name you entered with the `--login` option.