diff --git a/docs/modules/ROOT/pages/neo4j-arc/internals.adoc b/docs/modules/ROOT/pages/neo4j-arc/internals.adoc
index 520a1d27b5..793508ed86 100644
--- a/docs/modules/ROOT/pages/neo4j-arc/internals.adoc
+++ b/docs/modules/ROOT/pages/neo4j-arc/internals.adoc
@@ -92,13 +92,13 @@ This is how all those https://qubitpi.github.io/redux-observable/[Epics from red
 
 The "sender" of Suber bus is a graphing component who wants to persists some data into Neo4j database. For example,
 when we
-link:./graph-interaction/index.html#_how_graph_interations_take_effect_on_displayed_graph_and_backing_database[add a new node]
+link:../graph-interaction/index.html#_how_graph_interations_take_effect_on_displayed_graph_and_backing_database[add a new node]
 onto canvas, the graphing component initiates a Cypher query and
 https://github.com/oskarhane/suber?tab=readme-ov-file#self[feeds it into the Suber bus].
 
 We now know who the "sender" is at one end of Suber bus. Who is the receiver them? In its simplest form, our receiver
-can simply be https://qubitpi.github.io/redux-observable/[regular TypeScript class]. We also notice that Suber works
-with Redux. So how about having Redux as our "reciver"?
+can simply be https://github.com/oskarhane/suber?tab=readme-ov-file#usage[regular TypeScript class]. We also notice that
+Suber works with Redux. So how about having Redux as our "reciver"?
 
 If we do that, we will need to wire up some logic that sends the Cypher query against Neo4j database.
 *https://redux.qubitpi.org/tutorials/fundamentals/part-4-store/#middleware[Redux middleware] combined with