Use is_expected.to instead of should

style/README.md

@@ -270,13 +270,13 @@ Testing
 * Separate setup, exercise, verification, and teardown phases with newlines.
 * Use RSpec's [`expect` syntax].
 * Use RSpec's [`allow` syntax] for method stubs.
-* Use `should` shorthand for [one-liners with an implicit subject].
+* Use `is_expected.to` for [one-liners with an implicit subject].
 * Use `not_to` instead of `to_not` in RSpec expectations.
 * Prefer the `have_css` matcher to the `have_selector` matcher in Capybara assertions.
 
 [`expect` syntax]: http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
 [`allow` syntax]: https://github.com/rspec/rspec-mocks#method-stubs
-[one-liners with an implicit subject]: https://github.com/rspec/rspec-expectations/blob/master/Should.md#one-liners
+[one-liners with an implicit subject]: http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new_api_for_oneliners_
 
 #### Acceptance Tests
 

style/samples/testing.rb

@@ -1,6 +1,6 @@
 describe SomeClass do
-  it { should have_one(:association) }
-  it { should validate_presence_of(:some_attribute) }
+  it { is_expected.to have_one(:association) }
+  it { is_expected.to validate_presence_of(:some_attribute) }
 
   describe '.some_class_method' do
     it 'does something' do