fmt

stirby · stirby · commit a7f22be95b6f · 2024-11-01T17:02:00.000Z
diff --git a/docs/admin/templates/troubleshooting.md b/docs/admin/templates/troubleshooting.md
@@ -159,13 +159,12 @@ the top of the script to exit on error.
 
 If your workspaces are taking longer to start than expected, or longer than
 desired, you can diagnose which steps have the highest impact in the workspace
-build timings UI (available in v2.17 and beyond). Admins can can programmatically pull startup times for individual workspace builds using our
+build timings UI (available in v2.17 and beyond). Admins can can
+programmatically pull startup times for individual workspace builds using our
 [build timings API endpoint](../../reference/api/builds.md#get-workspace-build-timings-by-id).
 
-
 See our
 [guide on optimizing workspace build times](../../tutorials/best-practices/speed-up-templates.md)
 to optimize your templates based on this data.
 
 ![Workspace build timings UI](../../images/admin/templates/troubleshooting/workspace-build-timings-ui.png)
-
diff --git a/docs/user-guides/workspace-lifecycle.md b/docs/user-guides/workspace-lifecycle.md
@@ -111,9 +111,10 @@ workspace startup scripts.
 
 ## Workspace build times
 
-After a successful build, you can see a timing breakdown
-of the workspace startup process from the dashboard (starting in v2.17). We capture and display both time taken to
-provision the workspace's compute and agent startup steps. These include any
+After a successful build, you can see a timing breakdown of the workspace
+startup process from the dashboard (starting in v2.17). We capture and display
+both time taken to provision the workspace's compute and agent startup steps.
+These include any
 [`coder_script`](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/script)s
 such as [dotfiles](./workspace-dotfiles.md) or
 [`coder_app`](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/app)
