still proofreading, clarified a small thing - and added link/backlinnk to other reactive ui md doc

Author: ajeetgill

doc/guides/ReactiveUI.md

@@ -23,7 +23,7 @@ Use the simplest one that fits:
 1. **Slot binding** (`data$: this.name$`) — wire a changing value into a child component
 2. **`dot()`** (`this.data$.dot('name')`) — track a property inside a changing object
 3. **`map()`** (`this.count$.map(n => n + ' items')`) — transform a value for display
-4. **`dynamic()`** (`this.dynamic(function(mode) { ... })`) — rebuild DOM when structure changes
+4. **`dynamic()`** (`this.dynamic(function(mode) { ... })`) — rebuild DOM when dependent values change and you need different elements
 
 ---
 
@@ -415,6 +415,12 @@ why `this.add(function(prop) { ... })` behaves like `dynamic()`.
 
 ---
 
+## See Also
+
+- [Expressions vs dynamic()](dynamic.md) — covers how `expression` (model-level computed properties) differs from `this.dynamic()` (UI rendering), including evaluation semantics (lazy vs eager)
+
+---
+
 ## Gotchas
 
 1. **`data:` vs `data$:` is a one-character difference with big consequences**

doc/guides/dynamic.md

@@ -25,6 +25,10 @@ The implementation shows that `DynamicFunction` eagerly evaluates and always upd
 
 Both use FOAM's reactive slot system under the hood, but serve different purposes - expressions for computed model data and `this.dynamic()` for reactive UI rendering. The `DynamicFunction` implementation ensures UI updates happen immediately when dependencies change, while expressions only compute when accessed.
 
+## See Also
+
+- [Reactive UI Patterns](ReactiveUI.md) — covers `dynamic()` alongside the other three reactive UI patterns (`slot.dot()`, `slot.map()`, and slot binding via `prop$:`), with a decision framework for choosing between them
+
 Wiki pages you might want to explore:
 - [FOAM Framework Overview (kgrgreer/foam3)](/wiki/kgrgreer/foam3#1)
 - [Advanced Features and Extensions (kgrgreer/foam3)](/wiki/kgrgreer/foam3#7)