Update content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md

Author: hubwriter

content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md

@@ -14,7 +14,9 @@ topics:
 
 ## Overview
 
-The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define how long a codespace they have created can remain inactive before it times out. When a codespace times out it is stopped and will no longer incur charges for compute usage. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)."
+By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. 
+
+The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)."
 
 As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories.