Change Task titles to imperative. (#4022)

docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md

@@ -2,7 +2,7 @@
 redirect_from:
 - "/docs/user-guide/liveness/"
 - "/docs/user-guide.liveness.html"
-title: Configuring Liveness and Readiness Probes
+title: Configure Liveness and Readiness Probes
 ---
 
 {% capture overview %}
@@ -30,7 +30,7 @@ When a Pod is not ready, it is removed from Service load balancers.
 
 {% capture steps %}
 
-## Defining a liveness command
+## Define a liveness command
 
 Many applications running for long periods of time eventually transition to
 broken states, and cannot recover except by being restarted. Kubernetes provides
@@ -117,7 +117,7 @@ NAME            READY     STATUS    RESTARTS   AGE
 liveness-exec   1/1       Running   1          1m
 ```
 
-## Defining a liveness HTTP request
+## Define a liveness HTTP request
 
 Another kind of liveness probe uses an HTTP GET request. Here is the configuration
 file for a Pod that runs a container based on the `gcr.io/google_containers/liveness`
@@ -174,7 +174,7 @@ the Container has been restarted:
 kubectl describe pod liveness-http
 ```
 
-## Defining a TCP liveness probe
+## Define a TCP liveness probe
 
 A third type of liveness probe uses a TCP Socket. With this configuration, the
 kubelet will attempt to open a socket to your container on the specified port.
@@ -196,7 +196,7 @@ starts. Just like the readiness probe, this will attempt to connect to the
 `goproxy` container on port 8080. If the liveness probe fails, the container
 will be restarted.
 
-## Using a named port
+## Use a named port
 
 You can use a named
 [ContainerPort](/docs/api-reference/v1.6/#containerport-v1-core)
@@ -214,7 +214,7 @@ livenessProbe:
   port: liveness-port
 ```
 
-## Defining readiness probes
+## Define readiness probes
 
 Sometimes, applications are temporarily unable to serve traffic.
 For example, an application might need to load large data or configuration
@@ -244,7 +244,7 @@ Readiness and liveness probes can be used in parallel for the same container.
 Using both can ensure that traffic does not reach a container that is not ready
 for it, and that containers are restarted when they fail.
 
-## Configuring Probes
+## Configure Probes
 
 {% comment %}
 Eventually, some of this section could be moved to a concept topic.