README.md in pry-moves-0.1.4 vs README.md in pry-moves-0.1.5

@@ -1,7 +1,5 @@
-### Using [**pry-byebug**][pry-byebug] and not happy with commands behavior? We recommend this project instead
-
 # pry-moves
 
 _An execution control add-on for [Pry][pry]._
 
 * Install: `gem 'pry-moves'`
@@ -15,15 +13,16 @@
 * `f` - **finish** execution of current frame (block or method) and stop at next line on higher level
 * `c` - **continue**
 * `bt` - show latest 5 lines from backtrace
   * `bt 10` - latest 10 lines
   * `bt all` - full backtrace
-  * `bt >foo` - write backtrace to file `log/backtrace_foo.log`
+  * `bt > foo` - write backtrace to file `log/backtrace_foo.log`
 * `up`/`down`/`top`/`bottom` - move over call stack
   * `up +` - move up, including vapid frames (block callers, hidden frames)
   * `up pattern` - move up till first frame which method name or file position in format `folder/script.rb:12` matches regexp pattern
-* `debug some_method(param, param2)` - call `some_method(param, param2)` and interactively step into it
+* `debug some_method(some_param)` - call `some_method(some_param)` and interactively step into it. This way you can virtually "step back" by executing previous pieces of code from current method
+* `watch variable` - display variable's value on each step
 * `!` - exit
 
 
 ## Examples
 
@@ -94,10 +93,19 @@
 ```
 
 ## Performance
 
 Please note that debugging functionality is implemented through
-[`set_trace_func`][set_trace_func], which imposes certain performance penalty.
+[`set_trace_func`][set_trace_func], which imposes heavy performance penalty while tracing
+(while running code within `next`/`step`/`finish` commands).
+
+# Development
+
+## Testing
+
+```
+bundle exec rspec
+```
 
 ## Contributors
 
 * Gopal Patel ([@nixme](https://github.com/nixme))
 * John Mair ([@banister](https://github.com/banister))