From 6b16d4d4b81f603faa459d7a988445fa94c72447 Mon Sep 17 00:00:00 2001 From: Mohammed Al Sahaf Date: Sun, 5 Apr 2020 01:13:48 +0300 Subject: [PATCH] docs: fix the examples of the log format subdirective (#18) --- src/docs/markdown/caddyfile/directives/log.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/docs/markdown/caddyfile/directives/log.md b/src/docs/markdown/caddyfile/directives/log.md index 8ad5806..76b5a57 100644 --- a/src/docs/markdown/caddyfile/directives/log.md +++ b/src/docs/markdown/caddyfile/directives/log.md @@ -115,7 +115,7 @@ In addition to the syntax for each individual encoder, these common properties c The console encoder formats the log entry for human readability while preserving some structure. ``` -output console +format console ``` #### json @@ -123,7 +123,7 @@ output console Formats each log entry as a JSON object. ``` -output json +format json ``` #### logfmt @@ -131,7 +131,7 @@ output json Formats each log entry as [logfmt](https://brandur.org/logfmt). ``` -output logfmt +format logfmt ``` #### single_field @@ -139,7 +139,7 @@ output logfmt Writes only a single field from the structure log entry. Useful if one of the fields has all the information you need. ``` -output single_field +format single_field ``` - **<field_name>** is the name of the field whose value to use as the log entry.