diff --git a/logging/config/efk-logging-elasticsearch.adoc b/logging/config/efk-logging-elasticsearch.adoc
index 541d5831e0..681ad26205 100644
--- a/logging/config/efk-logging-elasticsearch.adoc
+++ b/logging/config/efk-logging-elasticsearch.adoc
@@ -1,6 +1,6 @@
 :context: efk-logging-elasticsearch
 [id="efk-logging-elasticsearch"]
-= Configuring Elasticsearch in {product-title}
+= Configuring Elasticsearch
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/logging/config/efk-logging-fluentd.adoc b/logging/config/efk-logging-fluentd.adoc
index 51e9af217c..588a8eefad 100644
--- a/logging/config/efk-logging-fluentd.adoc
+++ b/logging/config/efk-logging-fluentd.adoc
@@ -1,6 +1,6 @@
 :context: efk-logging-fluentd
 [id="efk-logging-fluentd"]
-= Configuring Fluentd in {product-title}
+= Configuring Fluentd
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/logging/config/efk-logging-kibana.adoc b/logging/config/efk-logging-kibana.adoc
index 98cf682621..1ca3f62545 100644
--- a/logging/config/efk-logging-kibana.adoc
+++ b/logging/config/efk-logging-kibana.adoc
@@ -1,6 +1,6 @@
 :context: efk-logging-kibana
 [id="efk-logging-kibana"]
-= Configuring Kibana in {product-title}
+= Configuring Kibana
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/logging/config/efk-logging-systemd.adoc b/logging/config/efk-logging-systemd.adoc
index b9bb787073..493cc4d34f 100644
--- a/logging/config/efk-logging-systemd.adoc
+++ b/logging/config/efk-logging-systemd.adoc
@@ -1,6 +1,6 @@
 :context: efk-logging-systemd
 [id="efk-logging-systemd"]
-= Configuring systemd-journald and rsyslog in {product-title}
+= Configuring systemd-journald and rsyslog
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/logging/efk-logging-eventrouter.adoc b/logging/efk-logging-eventrouter.adoc
index cd0eac2d08..e0f277d9ea 100644
--- a/logging/efk-logging-eventrouter.adoc
+++ b/logging/efk-logging-eventrouter.adoc
@@ -1,6 +1,6 @@
 :context: efk-logging-curator
 [id="efk-logging-eventrouter"]
-= Working with Event Router in {product-title}
+= Working with Event Router
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/logging/efk-logging-troubleshooting.adoc b/logging/efk-logging-troubleshooting.adoc
index 22908e8273..9777fa5e22 100644
--- a/logging/efk-logging-troubleshooting.adoc
+++ b/logging/efk-logging-troubleshooting.adoc
@@ -1,6 +1,6 @@
 :context: efk-logging-troubleshooting
 [id="efk-logging-troubleshooting"]
-= Troubleshooting Kibana in {product-title}
+= Troubleshooting Kibana
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/modules/efk-logging-about-curator.adoc b/modules/efk-logging-about-curator.adoc
index b66098d052..03732d23d1 100644
--- a/modules/efk-logging-about-curator.adoc
+++ b/modules/efk-logging-about-curator.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging.adoc
 
 [id="efk-logging-about-curator_{context}"]
-= About Curator in {product-title}
+= About Curator
 
 The Elasticsearch Curator tool performs scheduled maintenance operations on a global and/or on a per-project basis. Curator performs actions daily based on its configuration. Only one Curator Pod is
 recommended per Elasticsearch cluster. 
diff --git a/modules/efk-logging-about-elasticsearch.adoc b/modules/efk-logging-about-elasticsearch.adoc
index bb338269f5..141d33d746 100644
--- a/modules/efk-logging-about-elasticsearch.adoc
+++ b/modules/efk-logging-about-elasticsearch.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging.adoc
 
 [id="efk-logging-about-elasticsearch_{context}"]
-= About Elasticsearch in {product-title} 
+= About Elasticsearch 
 
 {product-title} uses link:https://www.elastic.co/products/elasticsearch[Elasticsearch (ES)] to organize the log data from Fluentd into datastores, or _indices_. 
 
diff --git a/modules/efk-logging-about-eventrouter.adoc b/modules/efk-logging-about-eventrouter.adoc
index c4fe34b297..fe9da1ff23 100644
--- a/modules/efk-logging-about-eventrouter.adoc
+++ b/modules/efk-logging-about-eventrouter.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging.adoc
 
 [id="efk-logging-about-eventrouter_{context}"]
-= About Event Router in {product-title}
+= About Event Router
 
 The Event Router is a pod that forwards {product-title} events to cluster logging.
 You must manually deploy Event Router.
diff --git a/modules/efk-logging-about-fluentd.adoc b/modules/efk-logging-about-fluentd.adoc
index 40bb6beebb..45fb13efa1 100644
--- a/modules/efk-logging-about-fluentd.adoc
+++ b/modules/efk-logging-about-fluentd.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging.adoc
 
 [id="efk-logging-about-fluentd_{context}"]
-= About Fluentd in {product-title}
+= About Fluentd
 
 {product-title} uses Fluentd to collect data about your cluster.
 
diff --git a/modules/efk-logging-about-kibana.adoc b/modules/efk-logging-about-kibana.adoc
index 993466c188..c4fca027e2 100644
--- a/modules/efk-logging-about-kibana.adoc
+++ b/modules/efk-logging-about-kibana.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging.adoc
 
 [id="efk-logging-about-kibana_{context}"]
-= About Kibana in {product-title}
+= About Kibana
 
 {product-title} uses Kibana to display the log data collected by Fluentd and indexed by Elasticsearch.
 
diff --git a/modules/efk-logging-about.adoc b/modules/efk-logging-about.adoc
index 27470e38ca..6d63cc73c0 100644
--- a/modules/efk-logging-about.adoc
+++ b/modules/efk-logging-about.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging.adoc
 
 [id="efk-logging-about_{context}"]
-= About cluster logging in {product-title}
+= About cluster logging
 
 As an {product-title} cluster administrator, you can deploy cluster logging to
 aggregate logs for a range of {product-title} services. 
diff --git a/modules/efk-logging-uninstall-efk-ops.adoc b/modules/efk-logging-uninstall-efk-ops.adoc
index 2783c07d10..c3c89e0d81 100644
--- a/modules/efk-logging-uninstall-efk-ops.adoc
+++ b/modules/efk-logging-uninstall-efk-ops.adoc
@@ -3,7 +3,7 @@
 // * logging/efk-logging-uninstall.adoc
 
 [id="efk-logging-uninstall-efk-ops_{context}"]
-= Uninstall the infra cluster in {product-title}
+= Uninstall the infra cluster
 
 You can uninstall the infra cluster from the {product-title} cluster logging. 
 After uninstalling, Fluentd no longer splits logs.
diff --git a/modules/nodes-cluster-overcommit-about.adoc b/modules/nodes-cluster-overcommit-about.adoc
index 8a9daaf993..735bc8c48d 100644
--- a/modules/nodes-cluster-overcommit-about.adoc
+++ b/modules/nodes-cluster-overcommit-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-cluster-overcommit.adoc
 
 [id="nodes-cluster-overcommit-about_{context}"]
-= Understanding overcommitment in {product-title}
+= Understanding overcommitment
 
 Requests and limits enable administrators to allow and manage the overcommitment of resources on a node. The scheduler uses requests for scheduling your container and providing a minimum service guarantee. Limits constrain the amount of compute resource that may be consumed on your node.
 
diff --git a/modules/nodes-cluster-overcommit-resource-requests.adoc b/modules/nodes-cluster-overcommit-resource-requests.adoc
index 88033817e6..ff3d620f97 100644
--- a/modules/nodes-cluster-overcommit-resource-requests.adoc
+++ b/modules/nodes-cluster-overcommit-resource-requests.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-cluster-overcommit.adoc
 
 [id="resource-requests_{context}"]
-= Understanding resource requests and overcommitment in {product-title}
+= Understanding resource requests and overcommitment
 
 For each compute resource, a container may specify a resource request and limit.
 Scheduling decisions are made based on the request to ensure that a node has
diff --git a/modules/nodes-cluster-resource-configure-oom.adoc b/modules/nodes-cluster-resource-configure-oom.adoc
index a46087fe72..89f176943c 100644
--- a/modules/nodes-cluster-resource-configure-oom.adoc
+++ b/modules/nodes-cluster-resource-configure-oom.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-cluster-resource-configure.adoc
 
 [id="nodes-cluster-resource-configure-oom_{context}"]
-= Understanding OOM kill policy in {product-title}
+= Understanding OOM kill policy
 
 {product-title} may kill a process in a container if the total memory usage of
 all the processes in the container exceeds the memory limit, or in serious cases
diff --git a/modules/nodes-containers-copying-files-rsync.adoc b/modules/nodes-containers-copying-files-rsync.adoc
index 75f2a486fc..4aca28a8a6 100644
--- a/modules/nodes-containers-copying-files-rsync.adoc
+++ b/modules/nodes-containers-copying-files-rsync.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-containers-copying-files.adoc
 
 [id="nodes-containers-copying-files-rsync_{context}"]
-= Using advanced Rsync features in {product-title}
+= Using advanced Rsync features
 
 The `oc rsync` command exposes fewer command line options than standard `rsync`.
 In the case that you wish to use a standard `rsync` command line option which is
diff --git a/modules/nodes-containers-events-about.adoc b/modules/nodes-containers-events-about.adoc
index 2adc5a4cb3..2583e4f500 100644
--- a/modules/nodes-containers-events-about.adoc
+++ b/modules/nodes-containers-events-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-containers-events.adoc
 
 [id="nodes-containers-events-about_{context}"]
-= Understanding events in {product-title}
+= Understanding events
 
 Events allow {product-title} to record
 information about real-world events in a resource-agnostic manner. They also
diff --git a/modules/nodes-containers-using-about.adoc b/modules/nodes-containers-using-about.adoc
index b24a106095..0213c6acec 100644
--- a/modules/nodes-containers-using-about.adoc
+++ b/modules/nodes-containers-using-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-containers-using.adoc
 
 [id="nodes-containers-using-about_{context}"]
-= Understanding Containers in {product-title} 
+= Understanding Containers 
 
 The basic units of {product-title} applications are called _containers_.
 link:https://access.redhat.com/articles/1353593[Linux container technologies]
diff --git a/modules/nodes-nodes-jobs-about.adoc b/modules/nodes-nodes-jobs-about.adoc
index 6287956739..34f5d2bd3f 100644
--- a/modules/nodes-nodes-jobs-about.adoc
+++ b/modules/nodes-nodes-jobs-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-nodes-jobs.adoc
 
 [id="nodes-nodes-jobs-about_{context}"]
-= Understanding jobs and CronJobs in {product-title}
+= Understanding jobs and CronJobs
 
 A job tracks the overall progress of a task and updates its status with information
 about active, succeeded, and failed pods. Deleting a job will clean up any pods it created.
diff --git a/modules/nodes-nodes-rebooting-infrastructure.adoc b/modules/nodes-nodes-rebooting-infrastructure.adoc
index 784a3c4e7f..e57e13f86a 100644
--- a/modules/nodes-nodes-rebooting-infrastructure.adoc
+++ b/modules/nodes-nodes-rebooting-infrastructure.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-nodes-rebooting.adoc
 
 [id="nodes-nodes-rebooting-infrastructure_{context}"]
-= Understanding infrastructure node rebooting in {product-title}
+= Understanding infrastructure node rebooting
 
 Infrastructure nodes are nodes that are labeled to run pieces of the
 {product-title} environment. Currently, the easiest way to manage node reboots
diff --git a/modules/nodes-pods-about.adoc b/modules/nodes-pods-about.adoc
index 0c2e1a0f1c..3efb24e71a 100644
--- a/modules/nodes-pods-about.adoc
+++ b/modules/nodes-pods-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-pods-using.adoc
 
 [id="nodes-pods-about_{context}"]
-= About pods in {product-title}
+= About pods
 
 {product-title} leverages the Kubernetes concept of a _pod_, which is one or more containers deployed
 together on one host, and the smallest compute unit that can be defined,
diff --git a/modules/nodes-pods-priority-about.adoc b/modules/nodes-pods-priority-about.adoc
index ebcd81ad5f..29c96413eb 100644
--- a/modules/nodes-pods-priority-about.adoc
+++ b/modules/nodes-pods-priority-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-pods-priority.adoc
 
 [id="nodes-pods-priority-about_{context}"]
-= Understanding pod priority in {product-title}
+= Understanding pod priority
 
 When you use the Pod Priority and Preemption feature, the scheduler orders pending pods by their priority, and a pending pod is placed ahead of other pending pods with lower priority in the scheduling queue. As a result, the higher priority pod might be scheduled sooner than pods with lower priority if its scheduling requirements are met. If a pod cannot be scheduled, scheduler continues to schedule other lower priority pods.
 
diff --git a/modules/nodes-pods-priority-preempt-about.adoc b/modules/nodes-pods-priority-preempt-about.adoc
index 31928756f6..d7bd692322 100644
--- a/modules/nodes-pods-priority-preempt-about.adoc
+++ b/modules/nodes-pods-priority-preempt-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-pods-priority.adoc
 
 [id="nodes-pods-priority-preempt-about_{context}"]
-= Understanding pod preemption in {product-title}
+= Understanding pod preemption
 
 When a developer creates a pod, the pod goes into a queue. If the developer configured the pod for pod priority or preemption, the scheduler picks a pod from the queue and tries to schedule the pod on a node. If the scheduler cannot find space on an appropriate node that satisfies all the specified requirements of the pod, preemption logic is triggered for the pending pod.
 
diff --git a/modules/nodes-pods-using-about.adoc b/modules/nodes-pods-using-about.adoc
index e99f678015..c55bcc995e 100644
--- a/modules/nodes-pods-using-about.adoc
+++ b/modules/nodes-pods-using-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-pods-using.adoc
 
 [id="nodes-pods-using-about_{context}"]
-= Understanding pods in {product-title} 
+= Understanding pods 
 
 Pods are the rough equivalent of a machine instance (physical or virtual) to a Container. Each pod is allocated its own internal IP address, therefore owning its entire port space, and Containers within pods can share their local storage and networking.
 
diff --git a/modules/nodes-pods-using-example.adoc b/modules/nodes-pods-using-example.adoc
index 811c017d6a..afb81677bc 100644
--- a/modules/nodes-pods-using-example.adoc
+++ b/modules/nodes-pods-using-example.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-pods-using.adoc
 
 [id="nodes-pods-using-example_{context}"]
-= Example pod configurations in {product-title}
+= Example pod configurations
 
 {product-title} leverages the Kubernetes concept of a _pod_, which is one or more Containers deployed
 together on one host, and the smallest compute unit that can be defined,
diff --git a/modules/nodes-scheduler-default-about.adoc b/modules/nodes-scheduler-default-about.adoc
index 61c510bbfe..8490be7a2d 100644
--- a/modules/nodes-scheduler-default-about.adoc
+++ b/modules/nodes-scheduler-default-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-default.adoc
 
 [id="nodes-scheduler-default-about_{context}"]
-= Understanding default scheduling in {product-title}
+= Understanding default scheduling
 
 The existing generic scheduler is the default platform-provided scheduler
 _engine_ that selects a node to host the pod in a three-step operation:
diff --git a/modules/nodes-scheduler-node-names-configuring.adoc b/modules/nodes-scheduler-node-names-configuring.adoc
index fcd33dcf4a..47bdf615b9 100644
--- a/modules/nodes-scheduler-node-names-configuring.adoc
+++ b/modules/nodes-scheduler-node-names-configuring.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-node-names.adoc
 
 [id="nodes-scheduler-node-name-configuring_{context}"]
-= Configuring the Pod Node Constraints admission controller to use names in {product-title}
+= Configuring the Pod Node Constraints admission controller to use names
 
 You can configure the Pod Node Constraints admission controller to ensure that pods are only placed onto nodes with a specific name.
 
diff --git a/modules/nodes-scheduler-node-projects-about.adoc b/modules/nodes-scheduler-node-projects-about.adoc
index dc31a45816..53af0070ba 100644
--- a/modules/nodes-scheduler-node-projects-about.adoc
+++ b/modules/nodes-scheduler-node-projects-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-node-projects.adoc
 
 [id="nodes-scheduler-node-projects-about_{context}"]
-= Understanding how to constrain pods by project name in {product-title}
+= Understanding how to constrain pods by project name
 
 The Pod Node Selector admission controller determines where a pod can be placed using labels on projects and node selectors specified in pods. A new pod will be placed on a node associated with a project only if the node selectors in the pod match the labels in the project.
 
diff --git a/modules/nodes-scheduler-node-projects-configuring.adoc b/modules/nodes-scheduler-node-projects-configuring.adoc
index 8962c41e07..fcc1f265e8 100644
--- a/modules/nodes-scheduler-node-projects-configuring.adoc
+++ b/modules/nodes-scheduler-node-projects-configuring.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-node-projects.adoc
 
 [id="nodes-scheduler-node-projects-configuring_{context}"]
-= Configuring the Pod Node Selector admission controller to use projects in {product-title}
+= Configuring the Pod Node Selector admission controller to use projects
 
 You can configure the Pod Node Selector admission controller to ensure that pods are only placed onto nodes in specific projects.
 The Pod Node Selector admission controller uses a configuration file to set options for the behavior of the backend. 
diff --git a/modules/nodes-scheduler-node-selectors-about.adoc b/modules/nodes-scheduler-node-selectors-about.adoc
index 4008fc351b..7e09027a63 100644
--- a/modules/nodes-scheduler-node-selectors-about.adoc
+++ b/modules/nodes-scheduler-node-selectors-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-node-selector.adoc
 
 [id="nodes-scheduler-node-selector-about_{context}"]
-= Understanding node selectors in {product-title}
+= Understanding node selectors
 
 Using _node selectors_, you can ensure that pods are only placed onto nodes with specific labels. As a cluster administrator, you can
 use the Pod Node Constraints admission controller to set a policy that prevents users without the *pods/binding* permission 
diff --git a/modules/nodes-scheduler-node-selectors-configuring.adoc b/modules/nodes-scheduler-node-selectors-configuring.adoc
index 10da8d2386..51ddaf190b 100644
--- a/modules/nodes-scheduler-node-selectors-configuring.adoc
+++ b/modules/nodes-scheduler-node-selectors-configuring.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-node-selector.adoc
 
 [id="nodes-scheduler-node-selectors-configuring_{context}"]
-= Configuring the Pod Node Constraints admission controller to use node selectors in {product-title}
+= Configuring the Pod Node Constraints admission controller to use node selectors
 
 You can configure the Pod Node Constraints admission controller to ensure that pods are only placed onto nodes with specific labels.
 
diff --git a/modules/nodes-scheduler-pod-affinity-about.adoc b/modules/nodes-scheduler-pod-affinity-about.adoc
index ee1eff7a36..a881fb48cc 100644
--- a/modules/nodes-scheduler-pod-affinity-about.adoc
+++ b/modules/nodes-scheduler-pod-affinity-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-pod-affinity.adoc
 
 [id="nodes-scheduler-pod-affinity-about_{context}"]
-= Understanding pod affinity in {product-title}
+= Understanding pod affinity
 
 _Pod affinity_ and _pod anti-affinity_ allow you to constrain which nodes your pod is eligible to be scheduled on based on the key/value labels on other pods. 
 
diff --git a/modules/nodes-scheduler-taints-tolerations-about.adoc b/modules/nodes-scheduler-taints-tolerations-about.adoc
index a8f097160a..e4805ea329 100644
--- a/modules/nodes-scheduler-taints-tolerations-about.adoc
+++ b/modules/nodes-scheduler-taints-tolerations-about.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-taints-tolerations.adoc
 
 [id="nodes-scheduler-taints-tolerations-about_{context}"]
-= Understanding taints and tolerations in {product-title}
+= Understanding taints and tolerations
 
 A _taint_ allows a node to refuse pod to be scheduled unless that pod has a matching _toleration_.
 
diff --git a/modules/nodes-scheduler-taints-tolerations-adding.adoc b/modules/nodes-scheduler-taints-tolerations-adding.adoc
index 1a7d1ed89a..7a1b3f0793 100644
--- a/modules/nodes-scheduler-taints-tolerations-adding.adoc
+++ b/modules/nodes-scheduler-taints-tolerations-adding.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-taints-tolerations.adoc
 
 [id="nodes-scheduler-taints-tolerations-adding_{context}"]
-= Adding taints and tolerations in {product-title}
+= Adding taints and tolerations
 
 You add taints to nodes and tolerations to pods allow the node to control which pods should (or should not) be scheduled on them.
 
diff --git a/modules/nodes-scheduler-taints-tolerations-examples.adoc b/modules/nodes-scheduler-taints-tolerations-examples.adoc
index 2551836877..df2518f4f0 100644
--- a/modules/nodes-scheduler-taints-tolerations-examples.adoc
+++ b/modules/nodes-scheduler-taints-tolerations-examples.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-taints-tolerations.adoc
 
 [id="nodes-scheduler-taints-tolerations-examples_{context}"]
-= Example taint and toleration scenarios in {product-title}
+= Example taint and toleration scenarios
 
 Taints and tolerations are a flexible way to steer pods away from nodes or evict pods that should not be running on a node. A few of typical scenarios are:
 
diff --git a/modules/nodes-scheduler-taints-tolerations-seconds.adoc b/modules/nodes-scheduler-taints-tolerations-seconds.adoc
index 724cb30e72..a8a788cb0a 100644
--- a/modules/nodes-scheduler-taints-tolerations-seconds.adoc
+++ b/modules/nodes-scheduler-taints-tolerations-seconds.adoc
@@ -3,7 +3,7 @@
 // * nodes/nodes-scheduler-taints-tolerations.adoc
 
 [id="nodes-scheduler-taints-tolerations-seconds_{context}"]
-= Setting a default value for toleration seconds in {product-title}
+= Setting a default value for toleration seconds
 
 When using taints and tolerations, if taints are added to an existing node, non-matching pods on that node will be evicted. You can modify the time allowed before pods are evicted using the toleration seconds plug-in, which sets the eviction period at five minutes, by default.
 
diff --git a/nodes/clusters/nodes-cluster-overcommit.adoc b/nodes/clusters/nodes-cluster-overcommit.adoc
index 9f6bfcdfc5..b61230ecc5 100644
--- a/nodes/clusters/nodes-cluster-overcommit.adoc
+++ b/nodes/clusters/nodes-cluster-overcommit.adoc
@@ -1,6 +1,6 @@
 :context: nodes-cluster-overcommit
 [id="nodes-cluster-overcommit"]
-= Configuring your cluster to place pods on overcommited nodes in {product-title} 
+= Configuring your cluster to place pods on overcommited nodes 
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/clusters/nodes-cluster-resource-configure.adoc b/nodes/clusters/nodes-cluster-resource-configure.adoc
index 5ea09a38fb..9628eebb8d 100644
--- a/nodes/clusters/nodes-cluster-resource-configure.adoc
+++ b/nodes/clusters/nodes-cluster-resource-configure.adoc
@@ -1,6 +1,6 @@
 :context: nodes-cluster-resource-configure
 [id="nodes-cluster-resource-configure"]
-= Configuring cluster memory to meet container memory and risk requirements in {product-title}
+= Configuring cluster memory to meet container memory and risk requirements
 include::modules/common-attributes.adoc[]
 
 
diff --git a/nodes/containers/nodes-containers-using.adoc b/nodes/containers/nodes-containers-using.adoc
index 264b0afa56..e7c84e2ad1 100644
--- a/nodes/containers/nodes-containers-using.adoc
+++ b/nodes/containers/nodes-containers-using.adoc
@@ -1,6 +1,6 @@
 :context: nodes-containers-using
 [id="nodes-containers-using"]
-= Understanding Containers in {product-title}
+= Understanding Containers
 include::modules/common-attributes.adoc[]
 
 
diff --git a/nodes/jobs/nodes-nodes-jobs.adoc b/nodes/jobs/nodes-nodes-jobs.adoc
index aa5fab5cf8..9fe7bb1d2f 100644
--- a/nodes/jobs/nodes-nodes-jobs.adoc
+++ b/nodes/jobs/nodes-nodes-jobs.adoc
@@ -1,7 +1,7 @@
 
 :context: nodes-nodes-jobs
 [id="nodes-nodes-jobs"]
-= Running tasks in pods using jobs in {product-title}
+= Running tasks in pods using jobs
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/jobs/nodes-pods-daemonsets.adoc b/nodes/jobs/nodes-pods-daemonsets.adoc
index 94c508ad98..3f78d35026 100644
--- a/nodes/jobs/nodes-pods-daemonsets.adoc
+++ b/nodes/jobs/nodes-pods-daemonsets.adoc
@@ -1,6 +1,6 @@
 :context: nodes-pods-daemonsets
 [id="nodes-pods-daemonsets"]
-=  Running background tasks on nodes automatically with daemonsets in {product-title}
+=  Running background tasks on nodes automatically with daemonsets
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/nodes/nodes-nodes-rebooting.adoc b/nodes/nodes/nodes-nodes-rebooting.adoc
index 5acb90f92a..c5fedebdfe 100644
--- a/nodes/nodes/nodes-nodes-rebooting.adoc
+++ b/nodes/nodes/nodes-nodes-rebooting.adoc
@@ -1,7 +1,7 @@
 
 :context: nodes-nodes-rebooting
 [id="nodes-nodes-rebooting"]
-= Understanding node rebooting in {product-title}
+= Understanding node rebooting
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/pods/nodes-pods-plugins.adoc b/nodes/pods/nodes-pods-plugins.adoc
index eed2be821b..fefe686dcc 100644
--- a/nodes/pods/nodes-pods-plugins.adoc
+++ b/nodes/pods/nodes-pods-plugins.adoc
@@ -1,6 +1,6 @@
 :context: nodes-pods-device
 [id="nodes-pods-device"]
-= Using device plug-ins to access external resouces with pods in {product-title}
+= Using device plug-ins to access external resouces with pods
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/pods/nodes-pods-priority.adoc b/nodes/pods/nodes-pods-priority.adoc
index ddc3b4bb79..aa86f26cb0 100644
--- a/nodes/pods/nodes-pods-priority.adoc
+++ b/nodes/pods/nodes-pods-priority.adoc
@@ -1,6 +1,6 @@
 :context: nodes-pods-priority
 [id="nodes-pods-priority"]
-= Including pod priority in pod scheduling decisions in {product-title}
+= Including pod priority in pod scheduling decisions
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/pods/nodes-pods-secrets.adoc b/nodes/pods/nodes-pods-secrets.adoc
index be898cc75d..0ee0a24ecc 100644
--- a/nodes/pods/nodes-pods-secrets.adoc
+++ b/nodes/pods/nodes-pods-secrets.adoc
@@ -1,6 +1,6 @@
 :context: nodes-pods-secrets
 [id="nodes-pods-secrets"]
-= Providing sensitive data to pods in {product-title}
+= Providing sensitive data to pods
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/pods/nodes-pods-using.adoc b/nodes/pods/nodes-pods-using.adoc
index 67208153d1..85ed346d01 100644
--- a/nodes/pods/nodes-pods-using.adoc
+++ b/nodes/pods/nodes-pods-using.adoc
@@ -1,6 +1,6 @@
 :context: nodes-pods-using-ssy
 [id="nodes-pods-using-pp"]
-= Using pods in {product-title}
+= Using pods
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/pods/nodes-pods-viewing.adoc b/nodes/pods/nodes-pods-viewing.adoc
index 460f7e3777..c58abdcf3e 100644
--- a/nodes/pods/nodes-pods-viewing.adoc
+++ b/nodes/pods/nodes-pods-viewing.adoc
@@ -1,6 +1,6 @@
 :context: nodes-pods-viewing
 [id="nodes-pods-viewing"]
-= Viewing pods in {product-title}
+= Viewing pods
 include::modules/common-attributes.adoc[]
 
 toc::[]
diff --git a/nodes/scheduling/nodes-scheduler-node-projects.adoc b/nodes/scheduling/nodes-scheduler-node-projects.adoc
index a3c3986801..d84a383949 100644
--- a/nodes/scheduling/nodes-scheduler-node-projects.adoc
+++ b/nodes/scheduling/nodes-scheduler-node-projects.adoc
@@ -1,6 +1,6 @@
 :context: nodes-scheduler-node-project
 [id="nodes-scheduler-node-project"]
-= Placing a pod in a specific project in {product-title}
+= Placing a pod in a specific project
 include::modules/common-attributes.adoc[]
 :relfileprefix: ../