From 01e168c100f571964e2602bc93ea826a93f456f7 Mon Sep 17 00:00:00 2001 From: Erik Winter Date: Thu, 7 Apr 2022 06:13:51 +0200 Subject: [PATCH] text edit --- doc/logging-in-golang.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/logging-in-golang.adoc b/doc/logging-in-golang.adoc index cc952e3..ec83c2b 100644 --- a/doc/logging-in-golang.adoc +++ b/doc/logging-in-golang.adoc @@ -7,7 +7,7 @@ The subject of logging comes up every now and then, in every group of developers Anyway, as with most things computing, I like logging to be simple and pragmatic. Over the years, these are the things I’ve come to consider important with this subject. * #levels[Levels] -* #structured-logging-and-standard-messages[Structured logging and standard messages] +* #structured-logging-and-standard-log-messages[Structured logging and standard log messages] * #wrapping-loggers[Wrapping loggers] * #advanced-structuring[Advanced structuring] * #injecting-loggers-versus-returning-errors[Injecting loggers versus returning errors]