From d0733d8769a168382b16caa5981ed04a5d45aa4e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gina=20H=C3=A4u=C3=9Fge?= <osd@foosel.net>
Date: Tue, 14 Jul 2015 09:10:14 +0200
Subject: [PATCH] Fixed a typo in the docs

logger => loggers in logging.yaml
---
 docs/configuration/logging_yaml.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/configuration/logging_yaml.rst b/docs/configuration/logging_yaml.rst
index daf8b462..54961188 100644
--- a/docs/configuration/logging_yaml.rst
+++ b/docs/configuration/logging_yaml.rst
@@ -17,7 +17,7 @@ Changing log levels
 If you need to change the default logging level within OctoPrint, create the file with a text editor of your choice
 (it's usually not there). The general format is this::
 
-    logger:
+    loggers:
       <component>:
         level: <loglevel>
 
@@ -27,7 +27,7 @@ new log level to set. An example for increasing the log level of the events and
 
 .. code-block:: yaml
 
-   logger:
+   loggers:
      octoprint.events:
        level: DEBUG
      octoprint.filemanager:
@@ -97,4 +97,4 @@ expressed in YAML as follows:
        format: "%(asctime)s - %(name)s - %(levelname)s - %(message)s"
 
 The possible keys for the logging format can be found in the
-`Python documentation on LogRecord attributes <https://docs.python.org/2/library/logging.html#logrecord-attributes>`_.
\ No newline at end of file
+`Python documentation on LogRecord attributes <https://docs.python.org/2/library/logging.html#logrecord-attributes>`_.