Add admonition type to shortcode (#9482)

* Change existing admon blocks

* Fix includes issue

content/en/docs/tasks/administer-federation/configmap.md

@@ -81,7 +81,7 @@ kubectl --context=federation-cluster delete configmap
 ```
 
 {{< note >}}
-**Note:** Deleting a Federated ConfigMap does not delete the corresponding ConfigMaps from underlying clusters. You must delete the underlying ConfigMaps manually.
+Deleting a Federated ConfigMap does not delete the corresponding ConfigMaps from underlying clusters. You must delete the underlying ConfigMaps manually.
 {{< /note >}}
 
 {{% /capture %}}

content/en/docs/tasks/administer-federation/hpa.md

@@ -87,7 +87,7 @@ max replicas on the federated HPA object, and the sum of minimum replicas will b
 than or equal to the minimum specified on the federated HPA object. 
 
 {{< note >}}
-**Note:** A particular cluster cannot have a minimum replica sum of 0.
+A particular cluster cannot have a minimum replica sum of 0.
 {{< /note >}}
 
 ### Spreading HPA min and max replicas in underlying clusters
@@ -125,8 +125,9 @@ in the previous section.
 You can delete a federated HPA as you would delete a Kubernetes
 HPA; however, for a federated HPA, you must send the request to
 the federation API server instead of to a specific Kubernetes cluster.
+
 {{< note >}}
-**Note:** For the federated resource to be deleted from all underlying clusters, [cascading deletion](/docs/concepts/cluster-administration/federation/#cascading-deletion) should be used.
+For the federated resource to be deleted from all underlying clusters, [cascading deletion](/docs/concepts/cluster-administration/federation/#cascading-deletion) should be used.
 {{< /note >}}
 
 For example, you can do that using `kubectl` by running:

content/en/docs/tasks/administer-federation/job.md

@@ -99,7 +99,7 @@ kubectl --context=federation-cluster delete job myjob
 ```
 
 {{< note >}}
-**Note:** Deleting a federated job will not delete the
+Deleting a federated job will not delete the
 corresponding jobs from underlying clusters.
 You must delete the underlying jobs manually.
 {{< /note >}}

content/en/docs/tasks/administer-federation/namespaces.md

@@ -84,7 +84,7 @@ As in Kubernetes, deleting a federated Namespace will delete all resources in th
 Namespace from the federation control plane.
 
 {{< note >}}
-**Note:** At this point, deleting a federated Namespace will not delete the corresponding Namespace, or resources in those Namespaces, from underlying clusters. Users must delete them manually. We intend to fix this in the future.
+At this point, deleting a federated Namespace will not delete the corresponding Namespace, or resources in those Namespaces, from underlying clusters. Users must delete them manually. We intend to fix this in the future.
 {{< /note >}}
 
 {{% /capture %}}

content/en/docs/tasks/administer-federation/replicaset.md

@@ -124,7 +124,7 @@ kubectl --context=federation-cluster delete rs myrs
 ```
 
 {{< note >}}
-**Note:** At this point, deleting a federated ReplicaSet will not delete the corresponding ReplicaSets from underlying clusters. You must delete the underlying ReplicaSets manually. We intend to fix this in the future.
+At this point, deleting a federated ReplicaSet will not delete the corresponding ReplicaSets from underlying clusters. You must delete the underlying ReplicaSets manually. We intend to fix this in the future.
 {{< /note >}}
 
 {{% /capture %}}

content/en/docs/tasks/administer-federation/secret.md

@@ -87,7 +87,7 @@ kubectl --context=federation-cluster delete secret mysecret
 ```
 
 {{< note >}}
-**Note:** At this point, deleting a federated secret will not delete the corresponding secrets from underlying clusters. You must delete the underlying secrets manually. We intend to fix this in the future.
+At this point, deleting a federated secret will not delete the corresponding secrets from underlying clusters. You must delete the underlying secrets manually. We intend to fix this in the future.
 {{< /note >}}
 
 {{% /capture %}}