diff --git a/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss b/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss
index 345aeb44d8c4..f95298eb86bc 100644
--- a/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss
+++ b/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss
@@ -90,8 +90,9 @@
       display: flex;
       gap: 1.5rem;
       flex-wrap: wrap;
-      justify-content: space-between;
+      justify-content: flex-start;
       align-items: center;
+      row-gap: 0.5rem;
     }
   }
 
diff --git a/adev/src/content/guide/routing/navigate-to-routes.md b/adev/src/content/guide/routing/navigate-to-routes.md
index c66e4f672cf6..e61a348e156c 100644
--- a/adev/src/content/guide/routing/navigate-to-routes.md
+++ b/adev/src/content/guide/routing/navigate-to-routes.md
@@ -146,7 +146,6 @@ export class UserDetail {
   }
 }
 ```
-
 ### `router.navigateByUrl()`
 
 The `router.navigateByUrl()` method provides a direct way to programmatically navigate using URL path strings rather than array segments. This method is ideal when you have a full URL path and need to perform absolute navigation, especially when working with externally provided URLs or deep linking scenarios.
diff --git a/adev/src/content/guide/signals/linked-signal.md b/adev/src/content/guide/signals/linked-signal.md
index e8169d3f9d2c..156d3ef6a920 100644
--- a/adev/src/content/guide/signals/linked-signal.md
+++ b/adev/src/content/guide/signals/linked-signal.md
@@ -54,6 +54,7 @@ shippingOptions.set(['Email', 'Will Call', 'Postal service']);
 console.log(selectedOption()); // 'Email'
 ```
 
+
 ## Accounting for previous state
 
 In some cases, the computation for a `linkedSignal` needs to account for the previous value of the `linkedSignal`.
@@ -133,3 +134,15 @@ const activeUserEditCopy = linkedSignal({
   equal: (a, b) => a.id === b.id,
 });
 ```
+
+## When to prefer `linkedSignal` over `computed`
+
+While `computed` is typically used to derive read-only state from other signals,
+`linkedSignal` is useful when the derived state should remain writable or
+preserve user-driven updates as its source changes.
+
+Use `linkedSignal` when the value depends on another signal but still needs to
+be explicitly set or updated in response to user interaction.
+
+Additionally, `linkedSignal` should be used when you need access to the previous
+state while reacting to a source signal.