From cc3c37cdb5ac823beef842e8091b3d1402570416 Mon Sep 17 00:00:00 2001 From: William Asper Date: Mon, 30 Dec 2019 19:24:21 -0800 Subject: [PATCH] Typo: change foreful to forceful --- v2:-Documentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2:-Documentation.md b/v2:-Documentation.md index e64ad08..05409a9 100644 --- a/v2:-Documentation.md +++ b/v2:-Documentation.md @@ -156,7 +156,7 @@ $ caddy stop [--address ] Gracefully stops the running Caddy process (other than the process for the stop command) and causes it to exit. -It first tries to use the admin API (at its default address, or you can customize it with the `--address` flag) to perform a graceful shutdown. In other words, it simply performs a request to the [/stop endpoint](#post-stop). If that fails for any reason, it will look for any other process named the same as the current binary (i.e. `os.Args[0]`) and signal it to stop gracefully. On Windows, such a stop is foreful and Caddy will not have an opportunity to clean up any active locks. +It first tries to use the admin API (at its default address, or you can customize it with the `--address` flag) to perform a graceful shutdown. In other words, it simply performs a request to the [/stop endpoint](#post-stop). If that fails for any reason, it will look for any other process named the same as the current binary (i.e. `os.Args[0]`) and signal it to stop gracefully. On Windows, such a stop is forceful and Caddy will not have an opportunity to clean up any active locks. If you want to stop the current configuration but do not want to exit the process, use the admin API: [`DELETE /config/`](#delete-configscope).