ENGDOCS-2221 (#20903)

content/manuals/compose/startup-order.md

@@ -52,6 +52,8 @@ Compose creates services in dependency order. `db` and `redis` are created befor
 
 Compose waits for healthchecks to pass on dependencies marked with `service_healthy`. `db` is expected to be "healthy" (as indicated by `healthcheck`) before `web` is created.
 
+`restart: true` ensures that if `db` is updated or restarted due to an explicit Compose operation, for example `docker compose restart`, the `web` service is also restarted automatically, ensuring it re-establishes connections or dependencies correctly.
+
 The healthcheck for the `db` service uses the `pg_isready -U ${POSTGRES_USER} -d ${POSTGRES_DB}'` command to check if the PostgreSQL database is ready. The service is retried every 10 seconds, up to 5 times.
 
 Compose also removes services in dependency order. `web` is removed before `db` and `redis`.

content/reference/compose-file/volumes.md

@@ -132,7 +132,7 @@ volumes:
 
 This makes it possible to make this lookup name a parameter of the Compose file, so that the model ID for the volume is hard-coded but the actual volume ID on the platform is set at runtime during deployment. 
 
-For example, if `DATABASE_VOLUME=my_volume_001` in your `.env` file:
+For example, if `DATABASE_VOLUME=my_volume_001` is in your `.env` file:
 
 ```yml
 volumes: