From e2c91466903b28ac237d4e8095cd0ca5bc534432 Mon Sep 17 00:00:00 2001
From: Luke Faraone <lfaraone@humbughq.com>
Date: Tue, 5 Feb 2013 16:00:00 -0500
Subject: [PATCH] Be more explicit as to where .humbugrc goes

(imported from commit 3e229d61ebfef64e29ca45cc57eca04ec207ae86)
---
 README            | 5 +++--
 examples/humbugrc | 2 +-
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/README b/README
index 0c93492..5b41bf1 100644
--- a/README
+++ b/README
@@ -22,8 +22,9 @@ as we make any changes to them.
 The easiest way to use these API bindings is to base your tools off
 of the example tools under examples/ in this distribution.
 
-If you place your API key in `~/.humbugrc` the Python API bindings will
-automatically read it in. The format of the config file is as follows:
+If you place your API key in the config file `~/.humbugrc` the Python
+API bindings will automatically read it in. The format of the config
+file is as follows:
 
     [api]
     key=<api key from the web interface>
diff --git a/examples/humbugrc b/examples/humbugrc
index 5e2bd33..0636fe1 100644
--- a/examples/humbugrc
+++ b/examples/humbugrc
@@ -1,4 +1,4 @@
-; put this file in ~/.humbugrc
+; Save this file as ~/.humbugrc
 [api]
 key=<api key from the web interface>
 email=<your email address>