Adding Callouts to Tasks > Inject Data Into Applications (#5023)

* Adding callout

* Adding callout

* Adding callouts

* Update distribute-credentials-secure.md

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

@@ -77,8 +77,9 @@ the techniques available for defining environment variables, including
 and
 [Secrets](/docs/concepts/configuration/secret/).
 
-NOTE: The environment variable appears in parentheses, `"$(VAR)"`. This is
+**Note:** The environment variable appears in parentheses, `"$(VAR)"`. This is
 required for the variable to be expanded in the `command` or `args` field.
+{: .note}
 
 ## Run a command in a shell
 

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

@@ -41,6 +41,7 @@ username and password:
 
     **Note:** If you want to skip the Base64 encoding step, you can create a Secret
     by using the `kubectl create secret` command:
+    {: .note}
 
        kubectl create secret generic test-secret --from-literal=username='my-app' --from-literal=password='39528$vdg7Jb'
 

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

@@ -46,8 +46,9 @@ The first element specifies that the value of the Pod's
 The second element specifies that the value of the Pod's `annotations`
 field should be stored in a file named `annotations`.
 
-**Note**: The fields in this example are Pod fields. They are not
+**Note:** The fields in this example are Pod fields. They are not
 fields of the Container in the Pod.
+{: .note}
 
 Create the Pod:
 
@@ -204,8 +205,9 @@ DownwardAPIVolumeFiles.
 * The Pod's labels
 * The Pod's annotations
 
-**Note**: If CPU and memory limits are not specified for a Container, the
+**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.
+{: .note}
 
 ## Project keys to specific paths and file permissions
 

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

@@ -51,8 +51,9 @@ The first element in the array specifies that the `MY_NODE_NAME` environment
 variable gets its value from the Pod's `spec.nodeName` field. Similarly, the
 other environment variables get their names from Pod fields.
 
-**Note**: The fields in this example are Pod fields. They are not fields of the
+**Note:** The fields in this example are Pod fields. They are not fields of the
 Container in the Pod.
+{: .note}
 
 Create the Pod: