wrap by note shortcodes (#9144)

content/en/docs/tutorials/stateful-application/basic-stateful-set.md

@@ -283,7 +283,8 @@ web-0
 web-1
 ```
 
-Note, if you instead see 403 Forbidden responses for the above curl command,
+{{< note >}}
+**Note:** if you instead see 403 Forbidden responses for the above curl command,
 you will need to fix the permissions of the directory mounted by the `volumeMounts`
 (due to a [bug when using hostPath volumes](https://github.com/kubernetes/kubernetes/issues/2630)) with:
 
@@ -292,6 +293,7 @@ for i in 0 1; do kubectl exec web-$i -- chmod 755 /usr/share/nginx/html; done
 ```
 
 before retrying the curl command above.
+{{< /note >}}
 
 In one terminal, watch the StatefulSet's Pods.
 

content/en/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md

@@ -71,13 +71,13 @@ A [Secret](/docs/concepts/configuration/secret/) is an object that stores a piec
 1. Create the Secret object from the following command. You will need to replace
    `YOUR_PASSWORD` with the password you want to use.
 
-      ```
+      ```shell
       kubectl create secret generic mysql-pass --from-literal=password=YOUR_PASSWORD
       ```
        
 2. Verify that the Secret exists by running the following command:
 
-      ```
+      ```shell
       kubectl get secrets
       ```
 
@@ -100,14 +100,14 @@ The following manifest describes a single-instance MySQL Deployment. The MySQL c
 
 1. Deploy MySQL from the `mysql-deployment.yaml` file:
 
-      ```
+      ```shell
       kubectl create -f mysql-deployment.yaml
       ```
 
 2. Verify that a PersistentVolume got dynamically provisioned. Note that it can
    It can take up to a few minutes for the PVs to be provisioned and bound.
 
-      ```
+      ```shell
       kubectl get pvc
       ```
 
@@ -120,11 +120,11 @@ The following manifest describes a single-instance MySQL Deployment. The MySQL c
 
 3. Verify that the Pod is running by running the following command:
 
-      ```
+      ```shell
       kubectl get pods
       ```
 
-      **Note:** It can take up to a few minutes for the Pod's Status to be `RUNNING`.
+      {{< note >}}**Note:** It can take up to a few minutes for the Pod's Status to be `RUNNING`.{{< /note >}}
 
       The response should be like this:
 
@@ -141,17 +141,17 @@ The following manifest describes a single-instance WordPress Deployment and Serv
 
 1. Create a WordPress Service and Deployment from the `wordpress-deployment.yaml` file:
 
-      ```
+      ```shell
       kubectl create -f wordpress-deployment.yaml
       ```
 
 2. Verify that a PersistentVolume got dynamically provisioned:
 
-      ``` 
+      ```shell
       kubectl get pvc
       ```
 
-      **Note:** It can take up to a few minutes for the PVs to be provisioned and bound.
+      {{< note >}}**Note:** It can take up to a few minutes for the PVs to be provisioned and bound.{{< /note >}}
 
       The response should be like this:
 
@@ -162,7 +162,7 @@ The following manifest describes a single-instance WordPress Deployment and Serv
 
 3. Verify that the Service is running by running the following command:
 
-      ```
+      ```shell
       kubectl get services wordpress
       ```
 
@@ -173,15 +173,11 @@ The following manifest describes a single-instance WordPress Deployment and Serv
       wordpress   10.0.0.89    <pending>     80:32406/TCP   4m
       ```
 
-      **Note:** Minikube can only expose Services through `NodePort`.
-
-      ```
-      The EXTERNAL-IP is always <pending>.
-      ```
+      {{< note >}}**Note:** Minikube can only expose Services through `NodePort`. The EXTERNAL-IP is always pending.{{< /note >}}
 
 4. Run the following command to get the IP Address for the WordPress Service:
 
-      ```
+      ```shell
       minikube service wordpress --url
       ```
 
@@ -207,20 +203,20 @@ The following manifest describes a single-instance WordPress Deployment and Serv
 
 1. Run the following command to delete your Secret:
 
-      ```
+      ```shell
       kubectl delete secret mysql-pass
       ```
 
 2. Run the following commands to delete all Deployments and Services:
 
-      ```
+      ```shell
       kubectl delete deployment -l app=wordpress
       kubectl delete service -l app=wordpress
       ```
 
 3. Run the following commands to delete the PersistentVolumeClaims.  The dynamically provisioned PersistentVolumes will be automatically deleted.
 
-      ```
+      ```shell
       kubectl delete pvc -l app=wordpress
       ```