[elpa] master b898fa3: packages/bug-hunter: Username and documentation

[Artur Malabarba]

branch: master
commit b898fa3d0cafc7ddd8e121178caa1a542013c9ca
Author: Artur Malabarba <address@hidden>
Commit: Artur Malabarba <address@hidden>

    packages/bug-hunter: Username and documentation
---
 packages/bug-hunter/README.org    |    1 +
 packages/bug-hunter/bug-hunter.el |   10 +++++-----
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/packages/bug-hunter/README.org b/packages/bug-hunter/README.org
index 78c622e..d8c9463 100644
--- a/packages/bug-hunter/README.org
+++ b/packages/bug-hunter/README.org
@@ -1,6 +1,7 @@
 #+OPTIONS: toc:nil num:nil
 #+TITLE: [[file:hunter.png]] The Bug Hunter 
[[https://travis-ci.org/Malabarba/elisp-bug-hunter][file:https://travis-ci.org/Malabarba/elisp-bug-hunter.svg?branch=master]]
 
+/Automatically debug and bisect your init (.emacs) file!/
 
 The Bug Hunter is an Emacs library that finds the source of an error
 or unexpected behavior inside an elisp configuration file (typically
diff --git a/packages/bug-hunter/bug-hunter.el 
b/packages/bug-hunter/bug-hunter.el
index 6faa5a1..041d5bd 100644
--- a/packages/bug-hunter/bug-hunter.el
+++ b/packages/bug-hunter/bug-hunter.el
@@ -1,10 +1,10 @@
-;;; bug-hunter.el --- Hunt down errors in elisp files  -*- lexical-binding: t; 
-*-
+;;; bug-hunter.el --- Hunt down errors by bisecting elisp files  -*- 
lexical-binding: t; -*-
 
 ;; Copyright (C) 2015 Free Software Foundation, Inc.
 
 ;; Author: Artur Malabarba <address@hidden>
-;; URL: http://github.com/Malabarba/elisp-bug-hunter
-;; Version: 1.0
+;; URL: https://github.com/Malabarba/elisp-bug-hunter
+;; Version: 1.0.1
 ;; Keywords: lisp
 ;; Package-Requires: ((seq "1.3") (cl-lib "0.5"))
 
@@ -110,7 +110,7 @@ non-nil in your current (problematic) Emacs state, AND that
 returns nil on a clean Emacs instance.
 If you're unsure how to write an assertion, you can try the interactive
 hunt instead, or see some examples in the Readme:
-    https://github.com/Bruce-Connor/elisp-bug-hunter";
+    https://github.com/Malabarba/elisp-bug-hunter";
   "Printed to the user if they provide a bad assertion.")
 
 (defvar bug-hunter--current-head nil
@@ -416,7 +416,7 @@ If you're looking for something that's not an error, use the
 interactive hunt instead of the error hunt.  If you have some
 elisp proficiency, you can also use the assertion hunt, see this
 link for some examples:
-    https://github.com/Bruce-Connor/elisp-bug-hunter";)
+    https://github.com/Malabarba/elisp-bug-hunter";)
         (or assertion "")))
 
      ;; Make sure we're in a forest, not a volcano.