Typo and whitespace fixes

Signed-off-by: Wincent Colaiuta <win@wincent.com>
Progress.
describe Rspec.configure instead of deprecated Spec::Runner.configure
define have_received for rspec2, re: issue #45
Merge pull request #65 from njay/patch-1

fix readme instructions for configuring to use rr mocks
Merge pull request #66 from njay/rspec2

have_received matchers for Rspec2 (fix issue #45)
Ensures RSpec2 adapter is required.
in the MiniTest adapter, raise a MiniTest::Assertion

that way, mock failures appear in the output as failures, rather
than uncaught exceptions.
README: Using RR examples for MiniTest and MiniSpec
README fix: Example in block syntax
First code example was not properly indented
making the first and last line to be unformatted
mis-spelling
Merge pull request #68 from james2m/rspec2

Rspec2 not being required.

Conflicts:
	Gemfile
	spec/spec_helper.rb
Merge pull request #88 from srbaker/master

Misspelled name
Merge pull request #85 from dabit/master

Small fix for README, block syntax section
Merge 'wincent/typos' into master (#41)
Merge pull request #69 from jayferd/minitest_assertion

in the MiniTest adapter, raise a MiniTest::Assertion
Merge pull request #72 from wynst/patch-1

README: Using RR examples for MiniTest and MiniSpec
Fix #44 (the flatten array bug)

The original bug was that if you did this

    require 'rr'
    include RR::Adapters::RRMethods
    mock(o = Object.new).some_random_method
    [o].flatten

then RR would complain with the following:

    NoMethodError: undefined method `to_ary' for #<Object:0x007feeba8336b8>

When you mock or stub a method on an object using RR, it will create a
method_missing method in the object's singleton class (assuming it is not there
already). This issue involves Array#flatten, which, in addition to calling
\#to_ary on each object in the array, also calls #method_missing on each object.
Now usually Array#flatten will swallow any NoMethodErrors that occur while
calling both #to_ary and #method_missing, but for some reason that is not
happening in this case. Regardless, we can combat this by supplying our own
version of #to_ary that returns nil. This tells Ruby to ignore our #to_ary and
use the default behavior in arrayifying our object in question.