link to workflow definitions on each definition

Author: flippedcoder

docs/production-deployment/worker-deployments/worker-versioning.mdx

@@ -81,11 +81,9 @@ To get started with Worker Versioning, you should understand some concepts aroun
   - Pinned Workflows are designed for use with rainbow deployments. See [Deployment Systems](#deployment-systems).
   - Pinned Workflows don't need to be patched, as they run on the same worker and build until they complete.
   - If you expect your Workflow to run longer than you want your Worker Deployment Versions to exist, you should mark your Workflow Type as Auto-Upgrade.
-- Each Worker Deployment has a single **Current Version** which is where Workflows are routed to unless they were previously pinned on a different version.
-- Each Worker Deployment can have a **Ramping Version** which is where a configurable percentage of Workflows are routed to unless they were previously pinned on a different version.
-- For a given Workflow, its **Target Worker Deployment Version** is the version it will move to next.
-
-You can find more details on the versioning types above in the [Worker Versioning encyclopedia article](/worker-versioning#versioning-definitions).
+- Each Worker Deployment has a single [**Current Version**](/worker-versioning#versioning-definitions) which is where Workflows are routed to unless they were previously pinned on a different version.
+- Each Worker Deployment can have a [**Ramping Version**](/worker-versioning#versioning-definitions) which is where a configurable percentage of Workflows are routed to unless they were previously pinned on a different version.
+- For a given Workflow, its [**Target Worker Deployment Version**](/worker-versioning#versioning-definitions) is the version it will move to next.
 
 ## Setting up your deployment system {#deployment-systems}