Change Task titles to imperative: Inject. (#4024)

_data/tasks.yml

@@ -25,7 +25,7 @@ toc:
   - docs/tasks/configure-pod-container/configure-pod-configmap.md
   - docs/tools/kompose/user-guide.md
 
-- title: Injecting Data Into Applications
+- title: Inject Data Into Applications
   section:
   - docs/tasks/inject-data-application/define-command-argument-container.md
   - docs/tasks/inject-data-application/define-environment-variable-container.md

docs/tasks/inject-data-application/define-command-argument-container.md

@@ -1,5 +1,5 @@
 ---
-title: Defining a Command and Arguments for a Container
+title: Define a Command and Arguments for a Container
 redirect_from:
 - "/docs/concepts/configuration/container-command-args/"
 - "/docs/concepts/configuration/container-command-arg.html"
@@ -22,7 +22,7 @@ in a Kubernetes Pod.
 
 {% capture steps %}
 
-## Defining a command and arguments when you create a Pod
+## Define a command and arguments when you create a Pod
 
 When you create a Pod, you can define a command and arguments for the
 containers that run in the Pod. To define a command, include the `command`
@@ -62,7 +62,7 @@ from the Pod:
         command-demo
         tcp://10.3.240.1:443
 
-## Using environment variables to define arguments
+## Use environment variables to define arguments
 
 In the preceding example, you defined the arguments directly by
 providing strings. As an alternative to providing strings directly,
@@ -83,7 +83,7 @@ and
 NOTE: The environment variable appears in parentheses, `"$(VAR)"`. This is
 required for the variable to be expanded in the `command` or `args` field.
 
-## Running a command in a shell
+## Run a command in a shell
 
 In some cases, you need your command to run in a shell. For example, your
 command might consist of several commands piped together, or it might be a shell

docs/tasks/inject-data-application/define-environment-variable-container.md

@@ -1,5 +1,5 @@
 ---
-title: Defining Environment Variables for a Container
+title: Define Environment Variables for a Container
 redirect_from:
 - "/docs/tasks/configure-pod-container/define-environment-variable-container/"
 - "/docs/tasks/configure-pod-container/define-environment-variable-container.html"
@@ -22,7 +22,7 @@ in a Kubernetes Pod.
 
 {% capture steps %}
 
-## Defining an environment variable for a container
+## Define an environment variable for a container
 
 When you create a Pod, you can set environment variables for the containers
 that run in the Pod. To set environment variables, include the `env` or

docs/tasks/inject-data-application/distribute-credentials-secure.md

@@ -1,5 +1,5 @@
 ---
-title: Distributing Credentials Securely Using Secrets
+title: Distribute Credentials Securely Using Secrets
 redirect_from:
 - "/docs/user-guide/secrets/walkthrough/"
 - "/docs/user-guide/secrets/walkthrough.html"
@@ -20,7 +20,7 @@ encryption keys, into Pods.
 
 {% capture steps %}
 
-## Converting your secret data to a base-64 representation
+## Convert your secret data to a base-64 representation
 
 Suppose you want to have two pieces of secret data: a username `my-app` and a password
 `39528$vdg7Jb`. First, use [Base64 encoding](https://www.base64encode.org/) to
@@ -33,7 +33,7 @@ example:
 The output shows that the base-64 representation of your username is `bXktYXBw`,
 and the base-64 representation of your password is `Mzk1MjgkdmRnN0pi`.
 
-## Creating a Secret
+## Create a Secret
 
 Here is a configuration file you can use to create a Secret that holds your
 username and password:
@@ -77,7 +77,7 @@ username and password:
         password:   13 bytes
         username:   7 bytes
 
-## Creating a Pod that has access to the secret data through a Volume
+## Create a Pod that has access to the secret data through a Volume
 
 Here is a configuration file you can use to create a Pod:
 
@@ -124,7 +124,7 @@ is exposed:
         my-app
         39528$vdg7Jb
 
-## Creating a Pod that has access to the secret data through environment variables
+## Create a Pod that has access to the secret data through environment variables
 
 Here is a configuration file you can use to create a Pod:
 

docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md

@@ -1,5 +1,5 @@
 ---
-title: Exposing Pod Information to Containers Through Files
+title: Expose Pod Information to Containers Through Files
 redirect_from:
 - "/docs/user-guide/downward-api/"
 - "/docs/user-guide/downward-api/index.html"
@@ -36,7 +36,7 @@ There are two ways to expose Pod and Container fields to a running Container:
 Together, these two ways of exposing Pod and Container fields are called the
 *Downward API*.
 
-## Storing Pod fields
+## Store Pod fields
 
 In this exercise, you create a Pod that has one Container.
 Here is the configuration file for the Pod:
@@ -147,7 +147,7 @@ Exit the shell:
 /# exit
 ```
 
-## Storing Container fields
+## Store Container fields
 
 The preceding exercise, you stored Pod fields in a DownwardAPIVolumeFile. 
 In this next exercise, you store Container fields. Here is the configuration
@@ -213,7 +213,7 @@ DownwardAPIVolumeFiles.
 **Note**: If CPU and memory limits are not specified for a Container, the
 Downward API defaults to the node allocatable value for CPU and memory.
 
-## Projecting keys to specific paths and file permissions
+## Project keys to specific paths and file permissions
 
 You can project keys to specific paths and specific permissions on a per-file
 basis. For more information, see

docs/tasks/inject-data-application/environment-variable-expose-pod-information.md

@@ -1,5 +1,5 @@
 ---
-title: Exposing Pod Information to Containers Through Environment Variables
+title: Expose Pod Information to Containers Through Environment Variables
 redirect_from:
 - "/docs/user-guide/environment-guide/"
 - "/docs/user-guide/environment-guide/index.html"
@@ -42,7 +42,7 @@ Together, these two ways of exposing Pod and Container fields are called the
 *Downward API*.
 
 
-## Using Pod fields as values for environment variables
+## Use Pod fields as values for environment variables
 
 In this exercise, you create a Pod that has one Container. Here is the
 configuration file for the Pod:
@@ -117,7 +117,7 @@ MY_NODE_NAME=minikube
 MY_POD_NAME=dapi-envars-fieldref
 ```
 
-## Using Container fields as values for environment variables
+## Use Container fields as values for environment variables
 
 In the preceding exercise, you used Pod fields as the values for environment
 variables. In this next exercise, you use Container fields as the values for

docs/tasks/inject-data-application/podpreset.md

@@ -1,7 +1,7 @@
 ---
 assignees:
 - jessfraz
-title: Injecting Information into Pods Using a PodPreset
+title: Inject Information into Pods Using a PodPreset
 redirect_from:
 - "/docs/user-guide/pod-preset/index/"
 - "/docs/user-guide/pod-preset/index.html"
@@ -54,7 +54,7 @@ modified by a `PodPreset`. The annotation is of the form
 `podpreset.admission.kubernetes.io/<pod-preset name>": "<resource version>"`.
 
 
-## Enabling Pod Preset
+## Enable Pod Preset
 
 In order to use Pod Presets in your cluster you must ensure the
 following
@@ -63,7 +63,7 @@ following
 1.  You have enabled the admission controller `PodPreset`
 1.  You have defined your pod presets
 
-## Creating a Pod Preset
+## Create a Pod Preset
 
 ### Simple Pod Spec Example