Change Task titles to imperative. (#4022)

docs/tasks/configure-pod-container/configure-service-account.md

@@ -3,7 +3,7 @@ assignees:
 - bprashanth
 - liggitt
 - thockin
-title: Configuring Service Accounts for Pods
+title: Configure Service Accounts for Pods
 redirect_from:
 - "/docs/user-guide/service-accounts/"
 - "/docs/user-guide/service-accounts.html"
@@ -26,7 +26,7 @@ cluster).  Processes in containers inside pods can also contact the apiserver.
 When they do, they are authenticated as a particular Service Account (e.g.
 `default`).
 
-## Using the Default Service Account to access the API server.
+## Use the Default Service Account to access the API server.
 
 When you create a pod, if you do not specify a service account, it is
 automatically assigned the `default` service account in the same namespace.
@@ -65,7 +65,7 @@ spec:
 
 The pod spec takes precedence over the service account if both specify a `automountServiceAccountToken` value.
 
-## Using Multiple Service Accounts.
+## Use Multiple Service Accounts.
 
 Every namespace has a default service account resource called `default`.
 You can list this and any other serviceAccount resources in the namespace with this command:
@@ -164,7 +164,7 @@ namespace: 7 bytes
 
 > Note that the content of `token` is elided here.
 
-## Adding ImagePullSecrets to a service account
+## Add ImagePullSecrets to a service account
 
 First, create an imagePullSecret, as described [here](/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
 Next, verify it has been created.  For example: