From 536aea15fb16412249bc5a5024d0959fa2d38d99 Mon Sep 17 00:00:00 2001 From: MohammadHasan Akbari <116190942+jarqvi@users.noreply.github.com> Date: Tue, 7 Oct 2025 12:15:25 +0330 Subject: [PATCH] Standardize phrasing to "at runtime" in Compose documentation (#23508) ## Description Standardized the phrasing from **"at run time"** to **"at runtime"** for consistency with other Docker documentation. No technical content changes. ## Related issues or tickets None. ## Reviews - [ ] Technical review - [x] Editorial review - [ ] Product review Signed-off-by: MohammadHasan Akbari --- .../how-tos/environment-variables/variable-interpolation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/manuals/compose/how-tos/environment-variables/variable-interpolation.md b/content/manuals/compose/how-tos/environment-variables/variable-interpolation.md index 04b1855346..820836559b 100644 --- a/content/manuals/compose/how-tos/environment-variables/variable-interpolation.md +++ b/content/manuals/compose/how-tos/environment-variables/variable-interpolation.md @@ -12,9 +12,9 @@ aliases: A Compose file can use variables to offer more flexibility. If you want to quickly switch between image tags to test multiple versions, or want to adjust a volume source to your local -environment, you don't need to edit the Compose file each time, you can just set variables that insert values into your Compose file at run time. +environment, you don't need to edit the Compose file each time, you can just set variables that insert values into your Compose file at runtime. -Interpolation can also be used to insert values into your Compose file at run time, which is then used to pass variables into your container's environment +Interpolation can also be used to insert values into your Compose file at runtime, which is then used to pass variables into your container's environment Below is a simple example: