updating feature docs to reflect capybara 2.3.0 dependency

change made in 8254ddc10c8e34912300ca2c8df275cc5132d1ba
The point of my suggestion is to make it possible to continue bumping a capybara version number to programmatically message users about the version we recommend they use.  As things stand now, we can't do that.