Readme.md in rack-webconsole-pry-0.1.5 vs Readme.md in rack-webconsole-pry-0.1.6
- old
+ new
@@ -1,16 +1,16 @@
-#rack-webconsole [](http://travis-ci.org/mrbrdo/rack-webconsole.png)
+#rack-webconsole-pry [](http://travis-ci.org/mrbrdo/rack-webconsole.png)
-Rack-webconsole is a Rack-based interactive console (à la Rails console) in
+rack-webconsole-pry is a Rack-based interactive console (à la Rails console) in
your web application's frontend. That means you can interact with your
application's backend from within the browser itself!
To get a clearer idea, you can check out this video showing a live example :)
[](http://youtu.be/yKK5J01Dqts?hd=1)
-Rack-webconsole is a Rack middleware designed to be unobtrusive. With Rails 3,
+rack-webconsole-pry is a Rack middleware designed to be unobtrusive. With Rails 3,
for example, you only have to include the gem in your Gemfile and it already
works. Without any configuration.
Tested with MRI versions 1.8.7, 1.9.2, ruby-head, and JRuby 1.6.3.
@@ -35,12 +35,12 @@
```ruby
gem 'rack-webconsole-pry', :require => 'rack-webconsole'
```
-Rack-webconsole **needs JQuery**. If you are using Rails 3, JQuery is loaded by
+rack-webconsole-pry **needs JQuery**. If you are using Rails 3, JQuery is loaded by
default. In case you don't want to use JQuery in your application,
-**rack-webconsole can inject it for you** only when it needs it. To do that you
+**rack-webconsole-pry can inject it for you** only when it needs it. To do that you
should put this line somewhere in your application (a Rails initializer, or
some configuration file):
```ruby
Rack::Webconsole.inject_jquery = true