diff --git a/pages/What is indentation and why does it matter%3F.md b/pages/What is indentation and why does it matter%3F.md
index efdc0a3..f5c7fbc 100644
--- a/pages/What is indentation and why does it matter%3F.md	
+++ b/pages/What is indentation and why does it matter%3F.md	
@@ -7,8 +7,8 @@ title:: What is indentation and why does it matter?
 	- Block **A** is a parent block; **B** and **C** are _children_ of **A**; block **D** is a _grandchild_ of **A**.
 	- Block **B** is a _child_ of **A** and it's in the same _branch_ as blocks **C** and **D**.
 	- Block **C** is a _child_ of **A** and the _parent_ of **D**.
-- Why is this important? As we've discussed in the previous lessons, Logseq is a networked note-taking tool that works with links. We also discussed that Logseq has no hierarchy, which is actually nuanced. As you've probably deduced by now, hierarchy in Logseq happens at the block level.
-- By indenting blocks, you create a branch that you can navigate. Let's turn the example above into links and navigate to the _**Linked references**_ section of the page of _Child **D,**_ created for block **D**:
+- Why is this important? As we've discussed in previous lessons, Logseq is a graph-based, networked note-taking tool. We mentioned that Logseq does not enforce a hierarchy—you can create all the hierarchies you need and modify them as your needs change. After all, a hierarchy is just one type of graph.
+- Anyway, hierarchy in Logseq happens at the block level. By indenting blocks, you create a branch that you can navigate. Let's turn the example above into links and navigate to the _**Linked references**_ section of the page of _Child **D,**_ created for block **D**:
 	- ![child-d-path.png](../assets/child-d-path_1641572255030_0.png)
 - By going to the page of _Child **D**_, we can see this hierarchy as it's composed on this documentation page: first up is _Parent and child **C**_ and then _Parent **A**_.
 - By clicking on one of the parents, the whole branch becomes visible: