@@ -30,7 +30,7 @@ Prebuilt workspaces are tightly integrated with [workspace presets](./parameters
3030
3131## Enable prebuilt workspaces for template presets
3232
33- In your template, add a ` prebuilds ` block within a ` coder_workspace_preset ` definition to identify how many prebuilt
33+ In your template, add a ` prebuilds ` block within a ` coder_workspace_preset ` definition to identify the number of prebuilt
3434instances your Coder deployment should maintain:
3535
3636 ``` hcl
@@ -71,7 +71,7 @@ Prebuilt workspaces follow a specific lifecycle from creation through eligibilit
7171 1 . The agent starts its bootstrap procedures and completes its startup scripts.
7272 1 . The agent reports ` ready ` status.
7373
74- Only once the agent reports ` ready ` is the prebuilt workspace considered eligible.
74+ After the agent reports ` ready ` , the prebuilt workspace considered eligible to be claimed .
7575
7676 Prebuilt workspaces that fail during provisioning are retried with a backoff to prevent transient failures.
7777
@@ -84,12 +84,11 @@ Prebuilt workspaces follow a specific lifecycle from creation through eligibilit
8484 [ ` coder_workspace_owner ` ] ( https://registry.terraform.io/providers/coder/coder/latest/docs/data-sources/workspace_owner )
8585 datasources (see [ Preventing resource replacement] ( #preventing-resource-replacement ) for further considerations).
8686
87- The process is transparent to the developer - they simply see a workspace ready faster than normal .
87+ The process is invisible to the developer - their workspace is ready faster than usual .
8888
8989You can view available prebuilt workspaces in the ** Workspaces** view in the Coder dashboard:
9090
9191![ A prebuilt workspace in the dashboard] ( ../../../images/admin/templates/extend-templates/prebuilt/prebuilt-workspaces.png )
92-
9392_ Note the search term ` owner:prebuilds ` ._
9493
9594### Template updates and the prebuilt workspace lifecycle
0 commit comments