updated the format for pricing page

docs/get-started/cost-billing/how-pricing-works.md

@@ -58,20 +58,32 @@ of the base SU for the maximum resource they reserve.
 
 - Project with 3 Pods with:
 
-     `1 vCPU, 3 GB RAM, 720hrs (24hr*30days)`
-     `0.1 vCPU, 8 GB RAM, 720hrs (24hr*30days)`
-     `2 vCPU, 4 GB RAM, 720hrs (24hr*30days)`
+    - `1 vCPU, 3 GB RAM, 720hrs (24hr*30days)`
+    - `0.1 vCPU, 8 GB RAM, 720hrs (24hr*30days)`
+    - `2 vCPU, 4 GB RAM, 720hrs (24hr*30days)`
 
-- Will be charged:
+- Project Will be charged:
 
     `RoundUP(Sum(`
+
     `1 CPU SUs due to first pod * 720hrs * $0.013`
+
     `2 CPU SUs due to extra RAM (8GB vs 0.4GB(0.1*4GB)) * 720hrs * $0.013`
-    `2 CPU SUs due to more CPU (2vCPU vs 1vCPU(4GB/4)) * 720hrs * $0.013))`
+
+    `2 CPU SUs due to more CPU (2vCPU vs 1vCPU(4GB/4)) * 720hrs * $0.013`
+
+    `))`
+
     `=RoundUP(Sum(720(1+2+2)))*0.013`
 
     `$46.80`
 
+!!! note "How to calculate cost for all running OpenShift pods?"
+    If you prefer a function for the OpenShift pods here it is:
+
+    `Project SU HR count = RoundUP(SUM(Pod1 SU hour count + Pod2 SU hr count +
+    ...))`
+
 OpenShift Pods are summed up to the project level so that fractions of CPU/RAM
 that some pods use will not get overcharged. There will be a split between CPU and
 GPU pods, as GPU pods cannot currently share resources with CPU pods.