updated definitions section title

Author: flippedcoder

docs/encyclopedia/workers/worker-versioning.mdx

@@ -22,6 +22,7 @@ This page defines some of the underlying concepts used in [Worker Versioning](/p
 - [Worker Deployments](#deployments)
 - [Worker Deployment Versions](#deployment-versions)
 - [Versioning Behaviors](#versioning-behaviors)
+- [Versioning Definitions](#versioning-definitions)
 - [Versioning Statuses](#versioning-statuses)
 - [Continue-as-new, Child Workflow, and Retry Semantics](#inheritance-semantics)
 
@@ -48,7 +49,7 @@ A **Pinned** Workflow is guaranteed to complete on a single Worker Deployment Ve
 
 An **Auto-Upgrade** Workflow will move to the latest Worker Deployment Version automatically whenever you change the current version. Auto-upgrade Workflows are not restricted to a single Deployment Version and need to be kept replay-safe manually, i.e. with [patching](/workflow-definition#workflow-versioning).
 
-## Versioning Types
+## Versioning Definitions
 
 - **Current Worker Deployment Version**: the version where Workflows are routed to unless they were previously pinned on a different version. Other versions can continue polling to allow pinned Workflows to finish executing or in case you need to roll back. If no current version is specified, the default is unversioned.
 - **Ramping Worker Deployment Version**: the version where a configurable percentage of Workflows are routed to unless they were previously pinned on a different version. The ramp percentage can be in the range [0, 100]. Workflows that don't go to the Ramping Version will go to the Current Version. If no Ramping Version is specified, 100% of new Workflows and Auto-Upgrade Workflows will go to the Current Version.