docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx

@@ -100,14 +100,18 @@ Define your Serverless Containers services using tools like Terraform for a full
 
 ## Migration Strategies
 
-Progressive migration: You don't need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel for the platform. This approach minimizes risk and allows your team to learn as you go.
+**Progressive migration**
 
-API Migration: When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users.
+You do not need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel of the platform. This approach minimizes risk and allows your teams to learn as they go.
 
-Start small with Serverless Jobs
+**API Migration**
 
-If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running batch jobs, scripts, or automated tasks that run to completion.
+When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users.
+
+## Start small with Serverless Jobs
+
+If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion.
 
 Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the serverless container ecosystem before committing to migrating larger, more critical services.
 
-Quickstart of Serverless Jobs product (/serverless-jobs/quickstart/)
+Refer to the [Serverless Jobs quickstart guide](/serverless-jobs/quickstart/) to deploy your first job in a few minutes.