about summary refs log tree commit homepage
path: root/README
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2014-05-12 06:43:44 +0000
committerEric Wong <normalperson@yhbt.net>2014-05-12 06:43:44 +0000
commit2dd4c5c457fb658b5b85e20c5ec23c14ab5834de (patch)
treebf9cda66f63af21e43b316777260605746518768 /README
parent1f5f9b0d64af4f0fc741a7ce095bf33745c54abe (diff)
downloadclogger-2dd4c5c457fb658b5b85e20c5ec23c14ab5834de.tar.gz
In case I'm hit by a bus, the lesser evil is to allow the FSF
to update our license than to be stuck as LGPLv3-only in the
future.

Some documentation/gemspec formatting updates while I'm at it.
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 4 insertions, 4 deletions
diff --git a/README b/README
index 8685921..e125b6f 100644
--- a/README
+++ b/README
@@ -1,6 +1,6 @@
-= \Clogger - configurable request logging for Rack
+= clogger - configurable request logging for Rack
 
-\Clogger is Rack middleware for logging HTTP requests.  The log format
+clogger is Rack middleware for logging HTTP requests.  The log format
 is customizable so you can specify exactly which fields to log.
 
 == FEATURES
@@ -19,7 +19,7 @@ is customizable so you can specify exactly which fields to log.
     all bytes in the range of \x00-\x1F
 
 * multi-instance capable and (optionally) reentrant.  You can use
-  \Clogger in a multi-threaded server, and even multiple Cloggers logging
+  clogger in a multi-threaded server, and even multiple cloggers logging
   to different locations and different formats in the same process.
 
 * Pure Ruby version for non-MRI versions of Ruby (or via CLOGGER_PURE=1
@@ -28,7 +28,7 @@ is customizable so you can specify exactly which fields to log.
 
 == SYNOPSIS
 
-\Clogger may be loaded as Rack middleware in your config.ru:
+clogger may be loaded as Rack middleware in your config.ru:
 
   # ENV['CLOGGER_PURE'] = '1' # uncomment to disable C extension
   require "clogger"