change language

bpmct · bpmct · commit 3194403acd8f · 2023-07-17T02:38:17.000Z
diff --git a/docs/images/templates/template-schedule-settings.png b/docs/images/templates/template-schedule-settings.png
diff --git a/docs/templates/index.md b/docs/templates/index.md
@@ -73,9 +73,9 @@ coder templates create <template-name>
 
 While workspaces can auto-stop based on activity, users set this value per-workspace it can be continuously bumped to prevent a workspace from stopping. For large enterprises, this can drive up cloud cost and introduce security concerns, as workspaces are not kept up to date.
 
-To enforce auto-stopping, you can enforce a timeout for all workspaces, as well as a max session duration.
+To enforce auto-stopping, you can set an auto-stop interval to ensure workspaces are auto restarted or auto-stopped, regardless of user activity.
 
-![Workspace auto-stop settings](../images/templates/pre-filled-parameters.png)
+![Workspace auto-stop settings](../images/templates/template-schedule-settings.png)
 
 Stops occur during a user's [quiet hours](../workspaces.md#quiet-hours), which prevent interruptions. If a user is still using their workspace, they can postpone a restart up to 3 hours.
 
diff --git a/docs/workspaces.md b/docs/workspaces.md
@@ -45,21 +45,19 @@ In Coder, workspaces can auto-stop when the user is not actively using the works
 - Open tunnels (`coder port-forward`)
 - Open WebSockets (web terminal, [web IDEs](./ides/web-ides.md) such as code-server and JupyterLab)
 
-> [Custom activity](#TODO) can be registered via Coder's REST API, such as an ongoing data science pipeline.
+> [Custom activity](./admin/automation.md#workspace-agents) can be registered via Coder's REST API, such as an ongoing data science pipeline.
 
 Your workspace's auto-stop behavior can be seen in the dashboard. Template settings in Coder determine if users can alter their workspace schedules.
 
 ![TODO: use real screenshot](./images/workspaces/stops-after-3-hours.png)
 
-### Max session length (enterpise)
-
-Workspaces may also have a max session length, which enforces a stop or restart even if you are actively using your workspace.
-
-![TODO: use real screenshot](./images/workspaces/approaching-stop.png)
+### Auto-stop schedule
 
+Some templates may have an auto-stop schedule that ensures workspaces are stopped
+or restarted at a specific interval, regardless of activity. This occurs during quiet hours (see below) to avoid interrupting users..
 #### Quiet hours
 
-To avoid interruptions, users can establish their "quiet hours", which are by default set from midnight to 3 AM, during which these actions occur. Users can also extend the deadline by up to 2 hours if they are in the middle of important work.
+To avoid interruptions, you can establish "quiet hours", which are by default set from midnight to 3 AM, during which these actions occur. Users can also extend the deadline by up to 2 hours if they are in the middle of important work.
 
 Example:
 
@@ -79,13 +77,6 @@ user bumps
 
 Admin controls around workspace auto-stop are an enterprise feature. [Learn more here](./admin/template)
 
-### Max lifetime
-
-Max lifetime is a template-level setting that determines the number of hours a
-workspace can run before it is automatically shutdown, regardless of any
-active connections. This setting ensures workspaces do not run in perpetuity
-when connections are left open inadvertently.
-
 ## Updating workspaces
 
 Use the following command to update a workspace to the latest template version.
