address feedback

Author: lennessyy

docs/encyclopedia/workers/worker-versioning.mdx

@@ -34,6 +34,8 @@ Each Deployment has a name (such as your service name) and supports versioning t
 ## Worker Deployment Versions {#deployment-versions}
 
 A Worker Deployment Version represents an iteration of a Worker Deployment.
+Each Deployment Version is identified by a deployment name and a <span id="build-id">Build ID</span>.
+The deployment name groups related Workers across versions, and the Build ID identifies a specific release of your Worker code.
 Each Deployment Version consists of Workers that share the same code build and environment.
 When a Worker starts polling for Workflow and Activity Tasks, it reports its Deployment Version to the Temporal Server.
 

docs/production-deployment/worker-deployments/serverless-workers/index.mdx

@@ -2,7 +2,9 @@
 id: index
 title: Serverless Workers
 sidebar_label: Serverless Workers
-description: Deploy Temporal Workers on serverless compute providers. Temporal invokes your Worker when Tasks arrive, with no long-lived processes to manage.
+description:
+  Deploy Temporal Workers on serverless compute providers. Temporal invokes your Worker when Tasks arrive, with no
+  long-lived processes to manage.
 slug: /production-deployment/worker-deployments/serverless-workers
 toc_max_heading_level: 4
 keywords:
@@ -16,14 +18,15 @@ tags:
   - Serverless
 ---
 
-Serverless Workers let you run Temporal Workers on serverless compute like AWS Lambda.
-Deploy your Worker code to a serverless provider, configure a compute provider for the Worker Deployment Version, and Temporal invokes the Worker when Tasks arrive.
-There are no long-lived processes to provision or scale.
+Serverless Workers let you run Temporal Workers on serverless compute like AWS Lambda. Deploy your Worker code to a
+serverless provider, configure a compute provider for the Worker Deployment Version, and Temporal invokes the Worker
+when Tasks arrive. There are no long-lived processes to provision or scale.
 
-Temporal monitors Task Queues that have a compute provider configured.
-When a Task arrives and no Worker is polling, Temporal invokes the configured compute target.
-The Worker starts, processes available Tasks, and shuts down when the invocation window ends.
+Temporal monitors Task Queues that have a compute provider configured. When a Task arrives and no Worker is polling,
+Temporal invokes the configured compute target. The Worker starts, processes available Tasks, and shuts down when the
+invocation window ends.
 
 ## Supported providers
 
-- [**AWS Lambda**](/production-deployment/worker-deployments/serverless-workers/aws-lambda) - Deploy a Go SDK Worker as a Lambda function. Temporal assumes an IAM role in your AWS account to invoke the function when Tasks arrive.
+- [**AWS Lambda**](/production-deployment/worker-deployments/serverless-workers/aws-lambda) - Deploy a Serverless Worker
+  as a Lambda function. Temporal assumes an IAM role in your AWS account to invoke the function when Tasks arrive.