Bump version to 0.3.0

README.md

@@ -13,7 +13,7 @@ The asynchronous nature of RxRuby makes it hard to write good specs for code tha
 
 The goal of rx-rspec is to provide powerful matchers that lets you express your expectations in a traditional rspec-like synchronous manner.
 
-Currently, the ambition of this project is simply to support the use cases that I encounter in my own usage of RxRuby. Your pull requests are wellcome.
+Currently, the ambition of this project is simply to support the use cases that I encounter in my own usage of RxRuby. Your pull requests are welcome.
 
 ## Usage
 
@@ -38,6 +38,6 @@ end
 rx-spec include the following matchers:
 
 - **emit_nothing()** matches an observable that completes without emitting events or erroring.
-- **emit_exactly()** metches against all items produced by the observable and requires the observable to be completed.
+- **emit_exactly()** matches against all items produced by the observable and requires the observable to be completed.
 - **emit_first()** matches against the first elements of the observable, but does not require it to complete
 - **emit_include()** consumes elements until the expected elements have occurred

rx-rspec.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |spec|
   spec.name        = 'rx-rspec'
-  spec.version     = '0.2.0'
+  spec.version     = '0.3.0'
   spec.summary     = 'rspec testing support for RxRuby'
   spec.description = 'Writing specs for reactive streams is tricky both because of their asynchronous nature and because their next/error/completed semantics. The goal of rx-rspec is to provide powerful matchers that lets you express your expectations in a traditional rspec-like synchronous manner.'
   spec.authors     = ['Anders Qvist']