From d5ec2e3defcc017428f79e57fcd41475c1065d64 Mon Sep 17 00:00:00 2001 From: Billy Donahue Date: Mon, 26 Jan 2026 11:13:19 -0500 Subject: [PATCH] SERVER-117779 Fix typo: occured -> occurred in docs/logging.md (#46965) Co-authored-by: Bodhi Silberling GitOrigin-RevId: f76cd249fbaeafcf72cce8208fc46506167efce9 --- docs/logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/logging.md b/docs/logging.md index b29adede9c6..210e8e551e4 100644 --- a/docs/logging.md +++ b/docs/logging.md @@ -206,7 +206,7 @@ Fatal level log statements using `LOGV2_FATAL` perform `fassert` after logging, using the provided ID as assert id. `LOGV2_FATAL_NOTRACE` perform `fassertNoTrace` and `LOGV2_FATAL_CONTINUE` does not `fassert` allowing for continued execution. `LOGV2_FATAL_CONTINUE` is meant to be used when a fatal -error has occured but a different way of halting execution is desired such as +error has occurred but a different way of halting execution is desired such as `std::terminate` or `fassertFailedWithStatus`. `LOGV2_FATAL_OPTIONS` performs `fassert` by default like `LOGV2_FATAL` but this