From d156eb591e2dbe7172f5b99a2192acbcdbb2d008 Mon Sep 17 00:00:00 2001 From: Brian Anderson Date: Fri, 12 May 2017 14:15:55 -0700 Subject: [PATCH] Minor crate doc tweaks --- src/lib.rs | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/lib.rs b/src/lib.rs index efc1aa7..a290fa4 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -10,7 +10,7 @@ //! A lightweight logging facade. //! -//! A logging facade provides a single logging API that abstracts over the +//! The `log` crate provides a single logging API that abstracts over the //! actual logging implementation. Libraries can use the logging API provided //! by this crate, and the consumer of those libraries can choose the logging //! framework that is most suitable for its use case. @@ -19,11 +19,10 @@ //! implementation that ignores all log messages. The overhead in this case //! is very small - just an integer load, comparison and jump. //! -//! A log request consists of a target, a level, and a body. A target is a -//! string which defaults to the module path of the location of the log -//! request, though that default may be overridden. Logger implementations -//! typically use the target to filter requests based on some user -//! configuration. +//! A log request consists of a _target_, a _level_, and a _body_. A target is a +//! string which defaults to the module path of the location of the log request, +//! though that default may be overridden. Logger implementations typically use +//! the target to filter requests based on some user configuration. //! //! # Use //!