diff --git a/docs/concepts/abstractions/overview.md b/docs/concepts/abstractions/overview.md
index 8407eecf43..7665607858 100644
--- a/docs/concepts/abstractions/overview.md
+++ b/docs/concepts/abstractions/overview.md
@@ -1,4 +1,5 @@
 ---
+title: Kubernetes Objects
 ---
 
 {% capture overview %}
diff --git a/docs/concepts/abstractions/pod-termination.md b/docs/concepts/abstractions/pod-termination.md
new file mode 100644
index 0000000000..5276dae617
--- /dev/null
+++ b/docs/concepts/abstractions/pod-termination.md
@@ -0,0 +1,15 @@
+---
+---
+
+#### <a name="pod-termination"></a> Pod Termination
+
+Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps:
+
+1. You send a command or API call to terminate the Pod.
+1. Kubernetes updates the Pod status to reflect the time after which the Pod is to be considered "dead" (the time of the termination request plus the grace period).
+1. Kubernetes marks the Pod state as "Terminating" and stops sending traffic to the Pod.
+1. Kubernetes send a `TERM` signal to the Pod, indicating that the Pod should shut down.
+1. When the grace period expires, Kubernetes issues a `SIGKILL` to any processes still running in the Pod.
+1. Kubernetes removes the Pod from the API server on the Kubernetes Master.
+
+> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information.
\ No newline at end of file
diff --git a/docs/concepts/abstractions/pod.md b/docs/concepts/abstractions/pod.md
index fb65c8b33c..d41d2ad1ac 100644
--- a/docs/concepts/abstractions/pod.md
+++ b/docs/concepts/abstractions/pod.md
@@ -1,4 +1,5 @@
 ---
+title: Pods
 ---
 
 {% capture overview %}
@@ -9,7 +10,6 @@ This page provides an overview of `Pod`, the smallest deployable object in the K
 {:toc}
 
 {% capture body %}
-### Understanding Pods
 
 A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.
 
@@ -67,19 +67,6 @@ Some examples of Controllers that contain one or more pods include:
 
 In general, Controllers use a [Pod Template]() that you provide to create the Pods for which it is responsible.
 
-#### <a name="pod-termination"></a> Pod Termination
-
-Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps:
-
-1. You send a command or API call to terminate the Pod.
-1. Kubernetes updates the Pod status to reflect the time after which the Pod is to be considered "dead" (the time of the termination request plus the grace period).
-1. Kubernetes marks the Pod state as "Terminating" and stops sending traffic to the Pod.
-1. Kubernetes send a `TERM` signal to the Pod, indicating that the Pod should shut down.
-1. When the grace period expires, Kubernetes issues a `SIGKILL` to any processes still running in the Pod.
-1. Kubernetes removes the Pod from the API server on the Kubernetes Master.
-
-> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information.
-
 {% endcapture %}