fix bullets

Author: anita-flegg

managing-cf/scaling-cloud-controller.html.md.erb

@@ -3,7 +3,7 @@ title: Scaling Cloud Controller
 owner: CAPI
 ---
 
-This topic describes how and when to scale BOSH jobs in CAPI, and includes details about some key metrics, heuristics, and logs. 
+This topic describes how and when to scale BOSH jobs in CAPI, and includes details about some key metrics, heuristics, and logs.
 
 To inform some scaling decisions, check current CPU values by running `bosh instances --ps --vitals`.
 The **CPU User** value corresponds with the `system.cpu.user` metric and is scaled by the number of CPUs.
@@ -26,7 +26,7 @@ When you are determining whether to scale `cloud_controller_ng`, look for the fo
 
 Cloud Controller emits the following metrics:
 
-* `cc.requests.outstanding.gauge` or `cc.requests.outstanding` (deprecated) 
+* `cc.requests.outstanding.gauge` or `cc.requests.outstanding` (deprecated)
   * Thin: is at or consistently near 20.
   * Puma: is at or consistently near the total number of available Puma threads on the VM. You can calculate this with `Puma Workers x Puma Max Threads`.
 * `system.cpu.user`
@@ -99,6 +99,7 @@ This is because Thin operates in a single process and Ruby's Global Interpreter
 
 If there are any threads which had to wait for a free DB connection (indicated by `cc_db_connection_wait_duration_seconds`) it might be worth to increase the DB connection pool if possible.
 Threads waiting on free DB connections will cause delays in the web server's responses.
+
 * Thin: Connection pool size can be configured with: `ccdb.max_connections`
 * Puma: Connection pool size per process (main + workers) can be configured with: `cc.puma.max_db_connections_per_process`