Updating documentation

Author: davidkpiano

docs/guides/custom-controls.md

@@ -31,7 +31,7 @@ class MyCustomInput extends React.Component {
 
 However, this can get a bit tedious, especially for complex controls. Thankfully, there's an easier way.
 
-## Custom Controls with `<Control>`
+## Standard Custom Controls with `<Control>`
 
 With the `<Control>` component, a custom component can be passed into the `component={...}` prop, and standard control props and event handlers (such as `onChange`, `onBlur`, `onFocus`, `value`, etc.) will be mapped as expected:
 
@@ -84,6 +84,21 @@ By default, any props on `<Control>` that are _not_ part of the `Control.propTyp
 />
 ```
 
+## Special Custom Controls with `<Control.custom>`
+
+If you do _not_ want any standard property mappings (such as `onChange`, `onBlur`, etc.) passed down to your custom control component, use `<Control.custom>` and define your own mappings:
+
+```jsx
+<Control.custom
+  component={SpecialCustomText}
+  mapProps={{
+    onTextChange: (props) => props.onChange,
+    onLoseFocus: (props) => props.onBlur,
+    // etc.
+  }}
+/>
+```
+
 ## Model and View Values
 
 One important thing to keep in mind is that there is no single `value` for a `<Control>`; rather, there are two types of values (that are equivalent, more often than not):