README.md in envied-0.8.1 vs README.md in envied-0.8.2

@@ -135,12 +135,12 @@
 
 ```ruby
 # Envfile
 enable_defaults! { ENV['RACK_ENV'] == 'development' }
 
-variable :FORCE_SSL, :Boolean, default: false
-variable :PORT, :Integer, default: proc {|envied| envied.FORCE_SSL ? 443 : 80 }
+variable :FORCE_SSL, :boolean, default: 'false'
+variable :PORT, :integer, default: proc {|envied| envied.FORCE_SSL ? 443 : 80 }
 ```
 
 Please remember that ENVied only **reads** from ENV; it doesn't mutate ENV.
 Don't let setting a default for, say `RAILS_ENV`, give you the impression that `ENV['RAILS_ENV']` is set.  
 As a rule of thumb you should only use defaults:
@@ -150,17 +150,10 @@
 ### More examples
 
 * See the [examples](/examples)-folder for a more extensive Envfile
 * See [the Envfile](https://github.com/eval/bunny_drain/blob/c54d7d977afb5e23a92da7a2fd0d39f6a7e29bf1/Envfile) for the bunny_drain application
 
-## Rails & Spring
-
-Long story short: Checking the presence of ENV variables using `ENVied.require` *will* work (use the `init:rails`-task and you're all set).  
-What won't work: relying on values from `ENV` (and thus `ENVied`) somewhere in `config/**/*.rb` **if these values vary between environments**.
-
-See this [wiki-page](https://github.com/eval/envied/wiki/Spring-gotchas) for more background info.
-
 ## Command-line interface
 
 For help on a specific command, use `envied help <command>`.
 
 ```bash
@@ -182,10 +175,10 @@
 
 ```
 $ bundle exec envied extract
 ```
 
-This comes in handy when you're not using ENVied yet. It will find all `ENV['EKY']` and `ENV.fetch('KEY')` statements in your project.
+This comes in handy when you're not using ENVied yet. It will find all `ENV['KEY']` and `ENV.fetch('KEY')` statements in your project.
 
 It assumes a standard project layout (see the default value for the globs-option).
 
 ### ...check the config of a Heroku app?