diff --git a/components/treeview/data-binding/hierarchical-data.md b/components/treeview/data-binding/hierarchical-data.md
index 124f4928c2..78175009e3 100644
--- a/components/treeview/data-binding/hierarchical-data.md
+++ b/components/treeview/data-binding/hierarchical-data.md
@@ -11,10 +11,10 @@ position: 2
# Treeview Data Binding to Hierarchical Data
This article explains how to bind the TreeView for Blazor to hierarchical data.
-@[template](/_contentTemplates/treeview/basic-example.md#data-binding-basics-link)
+@[template](/_contentTemplates/treeview/basic-example.md#data-binding-basics-link)
-Hierarchical data means that the child items are provided in a property of the parent item. By default, the TreeView expects this property to be called `Items`, otherwise set the property name in the `ItemsField` parameter. If a certain node has children, it will render an expand icon. The `HasChildren` model property can override this, but it is not required for hierarchical data binding.
+Hierarchical data means that the child items are provided in a property of the parent item. By default, the TreeView expects this property to be called `Items`, otherwise set the property name in the `ItemsField` parameter. If a certain node has non-`null` child items collection, it will render an expand icon. The `HasChildren` model property can override this, but it is not required for hierarchical data binding.
The hierarchical data binding approach allows you have separate collections of data or different model types at each TreeView level. Note that the data binding settings are per level, so a certain level will always use the same bindings, regardless of the model they represent and their parent.
@@ -33,58 +33,58 @@ The example below uses two levels of hierarchy, but the same idea applies to any
Hierarchical data hold collections of the child items
-
-
-
-
+
+
+
+
@code {
- public IEnumerable HierarchicalData { get; set; }
- public IEnumerable