diff --git a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md
index 7a1341b..a04e2b1 100644
--- a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md
+++ b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md
@@ -308,8 +308,11 @@ If any of the pods had any issue, you might see like it has 0 (CERO) instances.
 In that case, you can try to resume/restart that specific deployment by executing the following Kubernetes CLI command using KUBECTL, like any of the following:
 
 `kubectl rollout resume <serviceName> `
+
 `kubectl rollout resume deployments/webspa `
+
 `kubectl rollout resume deployments/frontend `
+
 `kubectl rollout resume deployments/catalog `
 
 Then, check if the deployment was performed successfully by using the Kubernetes dashboard or by using the following command:
@@ -321,6 +324,7 @@ In order to explicitly scale out any specific service, you can also use KUBECTL.
 For instance, let's say you want to scale out the NGINX frontend or the CATALOG service to 5 instances. You just need to run any of the following commands:
 
 `kubectl scale --replicas=5 deployments/frontend`
+
 `kubectl scale --replicas=5 deployments/catalog `
 
 ### Autoscale