From aaca52bc2fcb254f65a5b0e3173635de7c9bb8d6 Mon Sep 17 00:00:00 2001
From: Olexander Gnatishin <gnat86@gmail.com>
Date: Tue, 17 Sep 2013 08:42:56 +0200
Subject: [PATCH] Update README: add explanation for the getCurrTarget()

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 20643b5e..aa87cbfa 100644
--- a/README.md
+++ b/README.md
@@ -243,6 +243,8 @@ The Hopscotch framework comes with a simple set of API calls with which you can
 
 * `hopscotch.getCurrTour()` - Returns the currently running tour.
 
+* `hopscotch.getCurrTarget()` - Returns the target object of the currently running step.
+
 * `hopscotch.getCurrStepNum()` - Returns the zero-based step number of the currently running tour.
 
 * `hopscotch.getState()` - Checks for tour state saved in sessionStorage/cookies and returns the state if it exists. Use this method to determine whether or not you should resume a tour.