From 66e5bce4472e2f4dd00ea7cfbfe64fe1a114ef49 Mon Sep 17 00:00:00 2001 From: Dennis Hume Date: Fri, 20 Dec 2024 10:49:00 -0600 Subject: [PATCH] Update docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md Co-authored-by: Nikki Everett --- .../management/settings/customizing-agent-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md index e4997a87ed5fc..726017a31251e 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md @@ -18,7 +18,7 @@ For [Kubernetes agents](/todo.md) deployed with the Dagster+ Helm chart, you'll ## Enabling user code server TTL -User code servers support a configurable time-to-live (TTL). The agent will spin down any user code servers that haven’t served requests recently and will spin them back up the next time they’re needed. Configuring TTL can save compute cost because user code servers will spend less time sitting idle. +User code servers support a configurable time-to-live (TTL). The agent will spin down any user code servers that haven't served requests recently and will spin them back up the next time they're needed. Configuring TTL can save compute cost because user code servers will spend less time sitting idle. To configure TTL: ```yaml