diff --git a/docs/encyclopedia/workers/task-routing-worker-sessions.mdx b/docs/encyclopedia/workers/task-routing-worker-sessions.mdx
index b3ba6455ad..0ff273670b 100644
--- a/docs/encyclopedia/workers/task-routing-worker-sessions.mdx
+++ b/docs/encyclopedia/workers/task-routing-worker-sessions.mdx
@@ -85,12 +85,18 @@ In this case, each type of box would have its own Task Queue and a Workflow can
 
 If your use case involves more than one priority, you can create one Task Queue per priority, with a Worker pool per priority.
 
+Alternatively, you can use [Task Queue Priority](/develop/task-queue-priority-fairness), which lets you assign priority levels to Tasks within a single Task Queue.
+This approach avoids the overhead of managing multiple Task Queues and separate Worker pools while still ensuring higher-priority Tasks are processed first.
+
 ### Versioning
 
 Task Routing is the simplest way to version your code.
 
 If you have a new backward-incompatible Activity Definition, start by using a different Task Queue.
 
+Alternatively, you can use [Worker Versioning](/worker-versioning), which lets you tag Workers with a version and route Workflow and Activity Tasks to specific versions without requiring separate Task Queues.
+Worker Versioning supports both Pinned Workflows (which complete on a single Worker Deployment Version) and Auto-Upgrade Workflows (which automatically move to the latest version).
+
 ## What is a Worker Session? {#worker-session}
 
 A Worker Session is a feature provided by some SDKs that provides a straightforward API for [Task Routing](#task-routing) to ensure that Activity Tasks are executed with the same Worker without requiring you to manually specify Task Queue names.