Callouts and other small formatting (#5022)

* Removing Extra Spaces

Issue 4602 | Configure Pods and Containers

* Update security-context.md

Adding callouts

* Update security-context.md

* Adding callout and fixing code block

* Removing extra space

* Adding callout

* Addling callouts

* Update assign-cpu-resource.md

* Adding callout

* Update configure-persistent-volume-storage.md

* Update configure-service-account.md

* Update quality-service-pod.md

* Update security-context.md

docs/tasks/configure-pod-container/security-context.md

@@ -294,9 +294,8 @@ bits 12 and 25 are set. Bit 12 is `CAP_NET_ADMIN`, and bit 25 is `CAP_SYS_TIME`.
 See [capability.h](https://github.com/torvalds/linux/blob/master/include/uapi/linux/capability.h)
 for definitions of the capability constants.
 
-**Note**: Linux capability constants have the form `CAP_XXX`. But when you list capabilities
-in your Container manifest, you must omit the `CAP_` portion of the constant. For example,
-to add `CAP_SYS_TIME`, include `SYS_TIME` in your list of capabilities.
+**Note:** Linux capability constants have the form `CAP_XXX`. But when you list capabilities in your Container manifest, you must omit the `CAP_` portion of the constant. For example, to add `CAP_SYS_TIME`, include `SYS_TIME` in your list of capabilities.
+{: .note}
 
 ## Assign SELinux labels to a Container
 
@@ -313,8 +312,8 @@ securityContext:
     level: "s0:c123,c456"
 ```
 
-**Note**: To assign SELinux labels, the SELinux security module must be loaded
-on the host operating system.
+**Note:** To assign SELinux labels, the SELinux security module must be loaded on the host operating system.
+{: .note}
 
 ## Discussion
 
@@ -333,9 +332,8 @@ need to set the `level` section. This sets the
 [Multi-Category Security (MCS)](https://selinuxproject.org/page/NB_MLS)
 label given to all Containers in the Pod as well as the Volumes.
 
-**Warning**: After you specify an MCS label for a Pod, all Pods with the same
-label will able to access the Volume. So if you need inter-Pod
-protection, you must ensure each Pod is assigned a unique MCS label.
+**Warning:** After you specify an MCS label for a Pod, all Pods with the same label will able to access the Volume. So if you need inter-Pod protection, you must ensure each Pod is assigned a unique MCS label.
+{: .warning}
 
 {% endcapture %}