README.md in pilfer-1.0.1 vs README.md in pilfer-1.0.2

@@ -186,12 +186,12 @@
 `:files_matching` option. This calls `Profiler#profile_files_matching` using
 the given regular expression.
 
 ```ruby
 matcher = %r{^#{Regexp.escape(Rails.root.to_s)}/(app|config|lib|vendor/plugin)}
-use Pilfer::Middleware, :profiler       => profiler,
-                        :files_matching => matcher
+use Pilfer::Middleware, :profiler     => profiler,
+                        :file_matcher => matcher
 ```
 
 You almost certainly don't want to profile _every_ request. Provide a block to
 determine if a profile should be run on the incoming request.
 
@@ -205,10 +205,10 @@
 The Rack environment is available to allow profiling on demand.
 
 ```ruby
 # Profile requests containing the query string ?profile=true
 use Pilfer::Middleware, :profiler => profiler do |env|
-  env.query_string.include? 'profile=true'
+  env["QUERY_STRING"].include? 'profile=true'
 end
 
 # Profile requests containing a header whose value matches a secret
 use Pilfer::Middleware, :profiler => profiler do |env|
   env['HTTP_PROFILE_AUTHORIZATION'] == 'super-secret'