fixing articles for {product-title}

kalexand-rh · kalexand-rh · commit 859d5ab38775 · 2019-04-10T10:53:36.000-04:00
diff --git a/installing/installing_aws/installing-aws-account.adoc b/installing/installing_aws/installing-aws-account.adoc
@@ -20,7 +20,7 @@ include::modules/installation-aws-regions.adoc[leveloffset=+1]
 
 .Next steps
 
-* Install a {product-title} cluster. You can
+* Install an {product-title} cluster. You can
 xref:../../installing/installing_aws/installing-aws-customizations.adoc[install a customized cluster]
 or xref:../../installing/installing_aws/installing-aws-default.adoc[quickly install a cluster]
 with default options.
diff --git a/logging/efk-logging.adoc b/logging/efk-logging.adoc
@@ -7,7 +7,7 @@ toc::[]
 
 
 
-As a {product-title} cluster administrator, you can deploy cluster logging to aggregate logs for a range of {product-title} services.   
+As an {product-title} cluster administrator, you can deploy cluster logging to aggregate logs for a range of {product-title} services.   
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference
diff --git a/machine_management/applying-autoscaling.adoc b/machine_management/applying-autoscaling.adoc
@@ -1,11 +1,11 @@
 [id="applying-autoscaling"]
-= Applying autoscaling to a {product-title} cluster
+= Applying autoscaling to an {product-title} cluster
 include::modules/common-attributes.adoc[]
 :context: applying-autoscaling
 
 toc::[]
 
-Applying autoscaling to a {product-title} cluster involves deploying a
+Applying autoscaling to an {product-title} cluster involves deploying a
 ClusterAutoscaler and then deploying MachineAutoscalers for each Machine type
 in your cluster.
 
diff --git a/modules/cli-logging-in-kubeadmin.adoc b/modules/cli-logging-in-kubeadmin.adoc
@@ -11,7 +11,7 @@ command line interface (CLI).
 
 .Prerequisites
 
-* Deploy a {product-title} cluster.
+* Deploy an {product-title} cluster.
 * Install the `oc` CLI.
 
 .Procedure
diff --git a/modules/configuration-resource-overview.adoc b/modules/configuration-resource-overview.adoc
@@ -60,7 +60,7 @@ the cluster administrator wants the operator to ignore or not manage.
 |===
 
 While you can complete many other customizations and configure other integrations
-with a {product-title} cluster, configuring these resources is a common first
+with an {product-title} cluster, configuring these resources is a common first
 step after you deploy a cluster.
 
 Like all Operators, the Configuration Resources are governed by
diff --git a/modules/identity-provider-basic-authentication-CR.adoc b/modules/identity-provider-basic-authentication-CR.adoc
@@ -40,10 +40,10 @@ CLI, are sent a `WWW-Authenticate` challenge header for this provider.
 console, are redirected to a login page backed by this provider.
 <4> Controls how mappings are established between this provider's identities and user objects.
 <5> URL accepting credentials in Basic authentication headers.
-<6> Optional: Reference to a {product-title} ConfigMap containing the 
+<6> Optional: Reference to an {product-title} ConfigMap containing the 
 PEM-encoded certificate authority bundle to use in validating server 
 certificates for the configured URL.
-<7> Optional: Reference to a {product-title} Secret containing the client
+<7> Optional: Reference to an {product-title} Secret containing the client
 certificate to present when making requests to the configured URL.
-<8> Reference to a {product-title} Secret containing the key for the
+<8> Reference to an {product-title} Secret containing the key for the
 client certificate. Required if `tlsClientCert` is specified.
diff --git a/modules/identity-provider-github-CR.adoc b/modules/identity-provider-github-CR.adoc
@@ -44,7 +44,7 @@ challenges.
 <3> When `true`, unauthenticated token requests from web clients, like the web
 console, are redirected to GitHub to log in.
 <4> Controls how mappings are established between this provider's identities and user objects.
-<5> Optional: Reference to a {product-title} ConfigMap containing the 
+<5> Optional: Reference to an {product-title} ConfigMap containing the 
 PEM-encoded certificate authority bundle to use in validating server 
 certificates for the configured URL. Only for use in GitHub Enterprise.
 <6> The client ID of a
diff --git a/modules/identity-provider-gitlab-CR.adoc b/modules/identity-provider-gitlab-CR.adoc
@@ -48,6 +48,6 @@ The application must be configured with a callback URL of
 issued by GitLab.
 <7> The host URL of a GitLab provider. This could either be `\https://gitlab.com/`
 or any other self hosted instance of GitLab.
-<8> Optional: Reference to a {product-title} ConfigMap containing the 
+<8> Optional: Reference to an {product-title} ConfigMap containing the 
 PEM-encoded certificate authority bundle to use in validating server 
 certificates for the configured URL.
diff --git a/modules/identity-provider-keystone-CR.adoc b/modules/identity-provider-keystone-CR.adoc
@@ -41,10 +41,10 @@ console, are redirected to a login page backed by this provider.
 <4> Controls how mappings are established between this provider's identities and user objects.
 <5> Keystone domain name. In Keystone, usernames are domain-specific. Only a single domain is supported.
 <6> The URL to use to connect to the Keystone server (required).
-<7> Optional: Reference to a {product-title} ConfigMap containing the 
+<7> Optional: Reference to an {product-title} ConfigMap containing the 
 PEM-encoded certificate authority bundle to use in validating server 
 certificates for the configured URL.
-<8> Optional: Reference to a {product-title} Secret containing the client 
+<8> Optional: Reference to an {product-title} Secret containing the client 
 certificate to present when making requests to the configured URL.
-<9> Reference to a {product-title} Secret containing the key for the 
+<9> Reference to an {product-title} Secret containing the key for the 
 client certificate. Required if `tlsClientCert` is specified.
diff --git a/modules/identity-provider-ldap-CR.adoc b/modules/identity-provider-ldap-CR.adoc
@@ -60,7 +60,7 @@ user for this identity. First non-empty attribute is used.
 <9> Optional DN to use to bind during the search phase.
 <10> Optional reference to an {product-title} Secret containing the bind
 password.
-<11> Optional: Reference to a {product-title} ConfigMap containing the 
+<11> Optional: Reference to an {product-title} ConfigMap containing the 
 PEM-encoded certificate authority bundle to use in validating server 
 certificates for the configured URL. Only used when `insecure` is `false`.
 <12> When `true`, no TLS connection is made to the server. When `false`,
diff --git a/modules/identity-provider-ldap-secret.adoc b/modules/identity-provider-ldap-secret.adoc
@@ -5,7 +5,7 @@
 [id="identity-provider-creating-ldap-secret-{context}"]
 = Creating the LDAP Secret
 
-To use the identity provider, you must define a {product-title} Secret
+To use the identity provider, you must define an {product-title} Secret
 that contains the bindPassword.
 
 * Define an {product-title} Secret that contains the bindPassword.
diff --git a/modules/identity-provider-oidc-CR.adoc b/modules/identity-provider-oidc-CR.adoc
@@ -104,7 +104,7 @@ spec:
         userInfo: https://myidp.example.com/oauth2/userinfo <7>
 
 ----
-<1> Optional: Reference to a {product-title} ConfigMap containing the 
+<1> Optional: Reference to an {product-title} ConfigMap containing the 
 PEM-encoded certificate authority bundle to use in validating server 
 certificates for the configured URL.
 <2> Optional list of scopes to request, in addition to the *openid* scope,
diff --git a/modules/identity-provider-provisioning-user-lookup-mapping.adoc b/modules/identity-provider-provisioning-user-lookup-mapping.adoc
@@ -21,7 +21,7 @@ the identity provider:
 $ oc create user <username>
 ----
 +
-For example, the following command creates a {product-title} User `bob`:
+For example, the following command creates an {product-title} User `bob`:
 +
 ----
 $ oc create user bob
diff --git a/modules/identity-provider-request-header-CR.adoc b/modules/identity-provider-request-header-CR.adoc
@@ -61,7 +61,7 @@ that will authenticate clients which expect `WWW-Authenticate` challenges, and
 then proxy them to `\https://_<namespace_route>_/oauth/authorize`.
 `${url}` is replaced with the current URL, escaped to be safe in a query parameter.
 `${query}` is replaced with the current query string.
-<7> Reference to a {product-title} ConfigMap containing a PEM-encoded 
+<7> Reference to an {product-title} ConfigMap containing a PEM-encoded 
 certificate bundle. Used as a trust anchor to validate the TLS 
 certificates presented by the remote server. If this file is not
 present or valid the identity provider is not honored.
diff --git a/modules/installation-configuration-parameters.adoc b/modules/installation-configuration-parameters.adoc
@@ -7,7 +7,7 @@
 [id="installation-configuration-parameters-{context}"]
 = Installation configuration parameters
 
-Before you deploy a {product-title} cluster, you provide parameter values to
+Before you deploy an {product-title} cluster, you provide parameter values to
 describe your Amazon Web Services (AWS) account and optionally customize your
 cluster's platform. When you create the `install-config.yaml` installation
 configuration file, you provide values for the required parameters through the
diff --git a/modules/machine-autoscaler-about.adoc b/modules/machine-autoscaler-about.adoc
@@ -6,7 +6,7 @@
 = About the MachineAutoscaler
 
 The MachineAutoscaler adjusts the number of Machines in the MachineSets that you
-deploy in a {product-title} cluster. You can scale both the default `worker`
+deploy in an {product-title} cluster. You can scale both the default `worker`
 MachineSet and any other MachineSets that you create. The MachineAutoscaler
 makes more Machines when the cluster runs out of resources to support more
 deployments.
diff --git a/modules/olm-creating-etcd-cluster-from-operator.adoc b/modules/olm-creating-etcd-cluster-from-operator.adoc
@@ -10,7 +10,7 @@ Operator, managed by the Operator Lifecycle Manager (OLM).
 
 .Prerequisites
 
-- Access to a {product-title} 4.0 cluster
+- Access to an {product-title} 4.0 cluster
 - etcd Operator already installed to the cluster by an administrator
 
 .Procedure
diff --git a/nodes/clusters/nodes-containers-events.adoc b/nodes/clusters/nodes-containers-events.adoc
@@ -1,6 +1,6 @@
 :context: nodes-containers-events
 [id="nodes-containers-events-{context}"]
-= Viewing system event information in a {product-title} cluster
+= Viewing system event information in an {product-title} cluster
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/containers/nodes-containers-remote-commands.adoc b/nodes/containers/nodes-containers-remote-commands.adoc
@@ -1,6 +1,6 @@
 :context: nodes-containers-remote-commands
 [id="nodes-containers-remote-commands-{context}"]
-= Executing remote commands in a {product-title} container
+= Executing remote commands in an {product-title} container
 include::modules/common-attributes.adoc[]
 
 toc::[]
@@ -9,7 +9,7 @@ toc::[]
 
 
 
-You can use the CLI to execute remote commands in a {product-title} container. 
+You can use the CLI to execute remote commands in an {product-title} container. 
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference
