README.md in feature_guard-0.1.2 vs README.md in feature_guard-0.2.1

@@ -58,9 +58,28 @@
 # true for 52.5% of checks (random)
 ```
 
 The optional second argument to`.allow?` can be of any type (e.g., user ID or name or even an object). It is hashed with the feature name to create a reproducible numeric value for checking whether to return true or false based on the current ramp-up value. With no second argument, `.allow?` uses a new random value on every call.
 
+To retrieve information on all binary-enabled/disabled features, use `.all_flags`:
+
+```ruby
+FeatureGuard.enable :my_feature
+FeatureGuard.enable :another_feature
+FeatureGuard.toggle :my_feature
+FeatureGuard.all_flags
+# {"my_feature"=>false, "another_feature"=>true}
+```
+
+To retrieve information on all ramp values, use `.all_ramps`:
+
+```ruby
+FeatureGuard.set_ramp :my_feature, 50
+FeatureGuard.set_ramp :another_feature, 30
+FeatureGuard.all_ramps
+# {"my_feature"=>50.0, "another_feature"=>30.0}
+```
+
 ## Configuration
 
 Optionally change the Redis client with:
 
 ```ruby