Add admonition type to shortcode (#9482)

* Change existing admon blocks

* Fix includes issue

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

@@ -35,7 +35,7 @@ If you define args, but do not define a command, the default command is used
 with your new arguments.
 
 {{< note >}}
-**Note:** the `command` field corresponds to `entrypoint` in some container
+The `command` field corresponds to `entrypoint` in some container
 runtimes. Refer to the [Notes](#notes) below.
 {{< /note >}}
 
@@ -85,7 +85,7 @@ and
 [Secrets](/docs/concepts/configuration/secret/).
 
 {{< note >}}
-**Note:** The environment variable appears in parentheses, `"$(VAR)"`. This is
+The environment variable appears in parentheses, `"$(VAR)"`. This is
 required for the variable to be expanded in the `command` or `args` field.
 {{< /note >}}
 

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

@@ -79,7 +79,7 @@ Pod:
 1. To exit the shell, enter `exit`.
 
 {{< note >}}
-**Note:** The environment variables set using the `env` or `envFrom` field
+The environment variables set using the `env` or `envFrom` field
 will override any environment variables specified in the container image.
 {{< /note >}}
 

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

@@ -42,9 +42,10 @@ username and password:
     ```shell
     kubectl create -f https://k8s.io/docs/tasks/inject-data-application/secret.yaml
     ```
-{{< note >}}
-**Note:** If you want to skip the Base64 encoding step, you can create a Secret by using the `kubectl create secret` command:
-{{< /note >}}
+    {{< note >}}
+    If you want to skip the Base64 encoding step, you can create a Secret by using the `kubectl create secret` command:
+    {{< /note >}}
+    
     ```shell
     kubectl create secret generic test-secret --from-literal=username='my-app' --from-literal=password='39528$vdg7Jb'
     ```
@@ -79,7 +80,7 @@ username and password:
 
 
 {{< note >}}
-**Note:** If you want to skip the Base64 encoding step, you can create a Secret
+If you want to skip the Base64 encoding step, you can create a Secret
 by using the `kubectl create secret` command:
 {{< /note >}}
 

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

@@ -49,7 +49,7 @@ The second element specifies that the value of the Pod's `annotations`
 field should be stored in a file named `annotations`.
 
 {{< note >}}
-**Note:** The fields in this example are Pod fields. They are not
+The fields in this example are Pod fields. They are not
 fields of the Container in the Pod.
 {{< /note >}}
 
@@ -139,7 +139,7 @@ atomically using
 [rename(2)](http://man7.org/linux/man-pages/man2/rename.2.html).
 
 {{< note >}}
-**Note:** A container using Downward API as a
+A container using Downward API as a
 [subPath](/docs/concepts/storage/volumes/#using-subpath) volume mount will not
 receive Downward API updates.
 {{< /note >}}
@@ -221,7 +221,7 @@ In addition, the following information is available through
 * `metadata.annotations` - all of the pod’s annotations, formatted as `annotation-key="escaped-annotation-value"` with one annotation per line
 
 {{< note >}}
-**Note:** If CPU and memory limits are not specified for a Container, the
+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 >}}
 

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

@@ -48,7 +48,7 @@ variable gets its value from the Pod's `spec.nodeName` field. Similarly, the
 other environment variables get their names from Pod fields.
 
 {{< note >}}
-**Note:** The fields in this example are Pod fields. They are not fields of the
+The fields in this example are Pod fields. They are not fields of the
 Container in the Pod.
 {{< /note >}}