Edited readme.

README.markdown

@@ -104,7 +104,7 @@ In the above examples we satisfy dependencies using constructor injection. For t
 
 ### IoC Haters
 
-Use the built-in static class instead of providing an instance via the constructor.  But don't blame us when your code is hard to unit test.
+Use the built in static class instead of providing an instance via the constructor.  But don't blame us when your code is hard to unit test.
 
 	Flipper.DoIfOn(new MyFeature(), () => 
 	{
@@ -143,3 +143,6 @@ The preceding examples create features using the base classes `BooleanFeature` a
 	    }
 	}
 
+### Missing Settings
+
+Settings have a `Missing` property.  The aforementioned base classes all use these settings to flip features, and they all treat a feature as `ON` if a feature is missing.  The logic of this default behavior is simple.  Features tend to move from `OFF` to `ON`.  We don't want a bunch of old settings hanging around.  So a removed setting make a feature `ON`.