From 1c9d05f0af01f73ce133a53d30539fe397e6983f Mon Sep 17 00:00:00 2001 From: Finomnis Date: Wed, 7 Feb 2024 13:47:55 +0100 Subject: [PATCH] Minor beautification --- examples/20_orchestrated_shutdown_order.rs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/examples/20_orchestrated_shutdown_order.rs b/examples/20_orchestrated_shutdown_order.rs index 00f3494..7873b35 100644 --- a/examples/20_orchestrated_shutdown_order.rs +++ b/examples/20_orchestrated_shutdown_order.rs @@ -1,6 +1,8 @@ -//! This example demonstrates how a parent subsystem could orchestrate the shutdown order of its children manually. +//! This example demonstrates how a parent subsystem could orchestrate +//! the shutdown order of its children manually. //! -//! This is done by spawning the children in 'detached' mode to prevent that the shutdown signal gets passed to the children. +//! This is done by spawning the children in 'detached' mode to prevent +//! that the shutdown signal gets passed to the children. //! Then, the parent calls `initialize_shutdown` on each child manually. use miette::Result;