From fe7bbffd9dff7da603930df9853c91ede09b8ab9 Mon Sep 17 00:00:00 2001 From: bagratte Date: Wed, 10 May 2023 16:10:09 +0400 Subject: [PATCH] Proofread Compose startup order (#17273) --- compose/startup-order.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compose/startup-order.md b/compose/startup-order.md index 99e24a6f27..7cda43da85 100644 --- a/compose/startup-order.md +++ b/compose/startup-order.md @@ -15,7 +15,7 @@ A good example of when you might use this is an application which needs to acces ## Control startup -On startup, Compose does not wait until a container is "ready", only until it's running. This can cause issues if, for example you have a relational database system that needs to start its own services before being able to handle incoming connections. +On startup, Compose does not wait until a container is "ready", only until it's running. This can cause issues if, for example, you have a relational database system that needs to start its own services before being able to handle incoming connections. The solution for detecting the ready state of a service is to use the `condition` attribute with one of the following options: