Add admonition type to shortcode (#9482)

* Change existing admon blocks

* Fix includes issue

content/en/docs/concepts/storage/storage-classes.md

@@ -123,8 +123,10 @@ the class or PV, so mount of the PV will simply fail if one is invalid.
 
 {{< feature-state for_k8s_version="v1.12" state="beta" >}}
 
-**Note:** This feature requires the `VolumeScheduling` feature gate to be
+{{< note >}}
+This feature requires the `VolumeScheduling` feature gate to be
 enabled.
+{{< /note >}}
 
 The `volumeBindingMode` field controls when [volume binding and dynamic
 provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur.
@@ -159,8 +161,10 @@ The following plugins support `WaitForFirstConsumer` with pre-created Persistent
 ### Allowed Topologies
 {{< feature-state for_k8s_version="v1.12" state="beta" >}}
 
-**Note:** This feature requires the `VolumeScheduling` feature gate to be
+{{< note >}}
+This feature requires the `VolumeScheduling` feature gate to be
 enabled.
+{{< /note >}}
 
 When a cluster operactor specifies the `WaitForFirstConsumer` volume binding mode, it is no longer necessary
 to restrict provisioning to specific topologies in most situations. However,
@@ -232,8 +236,10 @@ parameters:
   encrypting the volume. If none is supplied but `encrypted` is true, a key is
   generated by AWS. See AWS docs for valid ARN value.
 
-**Note:** `zone` and `zones` parameters are deprecated and replaced with
+{{< note >}}
+`zone` and `zones` parameters are deprecated and replaced with
 [allowedTopologies](#allowed-topologies)
+{{< /note >}}
 
 ### GCE PD
 
@@ -269,8 +275,10 @@ specified, Kubernetes will arbitrarily choose among the specified zones. If the
 `zones` parameter is omitted, Kubernetes will arbitrarily choose among zones
 managed by the cluster.
 
-**Note:** `zone` and `zones` parameters are deprecated and replaced with
+{{< note >}}
+`zone` and `zones` parameters are deprecated and replaced with
 [allowedTopologies](#allowed-topologies)
+{{< /note >}}
 
 ### Glusterfs