docs(combobox): clarifications on item selection and custom values

Author: marin-bratanov

components/combobox/custom-value.md

@@ -20,7 +20,7 @@ To enable custom user input set the `AllowCustom` parameter to `true`.
 
 When custom input is allowed, the [ValueChanged event]({%slug components/combobox/events%}) fires on every keystroke, and not when an item is selected, because the ComboBox component acts as a text input.
 
-When custom values are typed in, there will be no selected item in the ComboBox.
+When custom values are typed in, there may be no selected item in the ComboBox. See the [ComboBox Overview - Selected Item]({%slug components/combobox/overview%}#selected-item) article for details on when how item selection and `Value` work together.
 
 >caption Allow custom user input in the combo box
 

components/combobox/events.md

@@ -102,9 +102,9 @@ The `OnChange` event is suitable for handling custom values the user can enter a
 * `OnChange` does not prevent two-way binding (the `@bind-Value` syntax)
 * `OnChange` fires only when the user presses `Enter`, or blurs the input (for example, clicks outside of the combo box). It does not fire on every keystroke, even when `AllowCustom="true"`, and it does not fire when an item is selected from the dropdown.
 
-See the [ComboBox Overview - Selected Item]({%slug components/combobox/overview%}#selected-item) article for details on when the event fires and how item selection works.
+See the [ComboBox Overview - Selected Item]({%slug components/combobox/overview%}#selected-item) article for details on when the event fires and how item selection and `Value` work.
 
->caption Handle OnChange without custom values - you must write text that will match an item.
+>caption Handle OnChange without custom values - to get a value from the list, you must write text that will match the text of an item (e.g, "item 5").
 
 ````CSHTML
 @result

components/combobox/overview.md

@@ -94,13 +94,15 @@ The ComboBox will not always have a selected item, however, because it can act a
 
 Missing selection is most common when the initial value is `null` as data sources rarely have items with a `null` value, and/or when you want to let your users type in values that are not in your predefined set of options.
 
-If the user types text in the input, selection behaves according to the following table:
+>caption If the user types text in the input, selection behaves according to the following table:
 
 
-| User input matches the value of an item | AllowCustom=`true`   | AllowCustom=`false`                      |
+| User input matches | AllowCustom=`true`   | AllowCustom=`false`                      |
 |----------------------------|----------------------|------------------------------------------|
-| Yes                        | Matched item is selected. | Matching item is selected.               |
-| No                         | No item is selected. `Value` is updated to the custom one. | No item is selected. `Value` is updated to `default(typeof(Value))`. The `OnChange` event does not fire for the value clearing. |
+|  The `TextField` of an item | Matched item is selected. The `Value` is taken from the item. | Matched item is selected. The `Value` is taken from the item. |
+| The `ValueField` of an item | No item is selected. `Value` is updated to the custom one. | No item is selected. `Value` is updated to `default(typeof(Value))`. The `OnChange` event does not fire for the value clearing. |
+| No match | No item is selected. `Value` is updated to the custom one. | No item is selected. `Value` is updated to `default(typeof(Value))`. The `OnChange` event does not fire for the value clearing. |
+