From a92ec0977ff4d848d37380abaa7d19e3010dc44f Mon Sep 17 00:00:00 2001 From: Khushi Jain Date: Sat, 2 Mar 2024 17:35:58 +0530 Subject: [PATCH] Update supplementary-guidelines.md --- specification/logs/supplementary-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/logs/supplementary-guidelines.md b/specification/logs/supplementary-guidelines.md index 47284e45d79..56151f0da04 100644 --- a/specification/logs/supplementary-guidelines.md +++ b/specification/logs/supplementary-guidelines.md @@ -84,7 +84,7 @@ automatic context propagation by NOT explicitly setting `Context` when calling [emit a LogRecord](./bridge-api.md#emit-a-logrecord). Some log libraries have mechanisms specifically tailored for injecting -contextual information info logs, such as MDC in Log4j. When available, it may +contextual information into logs, such as MDC in Log4j. When available, it may be preferable to use these mechanisms to set the Context. A log appender can then fetch the Context and explicitly set it when calling [emit a LogRecord](./bridge-api.md#emit-a-logrecord). This allows the correct Context