Skip to content

Commit

Permalink
another overview heading revamp
Browse files Browse the repository at this point in the history
  • Loading branch information
mahmoud committed Jun 5, 2016
1 parent d00cc7d commit 5c66209
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/overview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ yourself asking, "How long does this part take?" then it's time to
``pip install lithoxyl``. There are two steps. First comes
instrumentation, then we get into configuration.

Records for instrumentation
---------------------------
Instrumenting with Records
--------------------------

With Lithoxyl, logging and other instrumentation starts with knowing
your application. We want to find the important parts of your
Expand Down Expand Up @@ -87,8 +87,8 @@ That about covers creating and interacting with records. Now we turn
to the origin and destination of the records we create and populate:
Loggers and Sinks.

Logger creation
---------------
Creating Loggers
----------------

Records make up most of an application's interaction with Lithoxyl,
but it would not be very easy to create a Record without a Logger.
Expand Down Expand Up @@ -120,8 +120,8 @@ your application, no matter how many aspects it may have. On their
own, they are conceptually useful, but without Sinks, they are all
potential.

BasicSink configuration
-----------------------
Configuring Sinks
-----------------

So far, we have discovered two uses of the Lithoxyl Logger:

Expand Down Expand Up @@ -150,7 +150,7 @@ monitoring thread or network service. Most developers expect
persistent logging to streams (stdout/stderr) and files. Lithoxyl is
more than capable.

Sensible logging
Logging Sensibly
----------------

For developers who want a sensible and practical default, Lithoxyl
Expand Down

0 comments on commit 5c66209

Please sign in to comment.