diff --git a/docs/deployment.md b/docs/deployment.md
index 2b9602b2a6144..287d84a4e3b0f 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -1,5 +1,5 @@
 ---
-description: Learn how to deploy your Next.js app to production either managed or self-hosted.
+description: Learn how to deploy your Next.js app to production, either managed or self-hosted.
 ---
 
 # Deployment
@@ -18,9 +18,9 @@ Congratulations, you are ready to deploy your Next.js application to production.
 This output is generated inside the `.next` folder:
 
 - `.next/chunks/pages` – Each JavaScript file inside this folder relates to the route with the same name. For example, `.next/chunks/pages/about.js` would be the JavaScript chunk loaded when viewing the `/about` route in your application
-- `.next/static/media` – Statically import images from `next/image` are hashed and copied here
+- `.next/static/media` – Statically imported images from `next/image` are hashed and copied here
 - `.next/static/css` – Global CSS files for all pages in your application
-- `.next/server/pages` – The HTML and JavaScript entry points prerendered from the server. The `.nft.json` files are used to understand how to [bundle dependencies](/docs/advanced-features/output-file-tracing.md)
+- `.next/server/pages` – The HTML and JavaScript entry points prerendered from the server. The `.nft.json` files are created when [Output File Tracing](/docs/advanced-features/output-file-tracing.md) is enabled and contain all the file paths that depend on a given page.
 - `.next/server/chunks` – Shared JavaScript chunks used in multiple places throughout your application
 - `.next/cache` – Output for the build cache and cached images, responses, and pages from the Next.js server. Using a cache helps decrease build times and improve performance of loading images
 
@@ -30,14 +30,14 @@ All JavaScript code inside `.next` has been **compiled** and browser bundles hav
 
 [Vercel](https://vercel.com/) is a frontend cloud platform from the creators of Next.js. It's the fastest way to deploy your managed Next.js application with zero configuration.
 
-When deploying to Vercel, the `next build` output is automatically transformed and optimized for you, including:
+When deploying to Vercel, the platform automatically detects Next.js, runs `next build`, and optimizes the build output for you, including:
 
 - Persisting cached assets across deployments if unchanged
-- Immutable deployments with a unique URL for every commit
+- [Immutable deployments](https://vercel.com/features/previews) with a unique URL for every commit
 - [Pages](/docs/basic-features/pages.md) are automatically statically optimized, if possible
 - Assets (JavaScript, CSS, images, fonts) are compressed and served from a [Global Edge Network](https://vercel.com/features/infrastructure)
 - [API Routes](/docs/api-routes/introduction.md) are automatically optimized as isolated [Serverless Functions](https://vercel.com/features/infrastructure) that can scale infinitely
-- [Middleware](/docs/middleware.md) are automatically optimized as [Edge Functions](https://vercel.com/edge) that have zero cold starts and boot instantly
+- [Middleware](/docs/middleware.md) are automatically optimized as [Edge Functions](https://vercel.com/features/edge-functions) that have zero cold starts and boot instantly
 
 In addition, Vercel provides features like:
 
@@ -47,7 +47,7 @@ In addition, Vercel provides features like:
 - Support for [Environment Variables](https://vercel.com/docs/environment-variables)
 - Support for [Custom Domains](https://vercel.com/docs/custom-domains)
 - Support for [Image Optimization](/docs/basic-features/image-optimization.md) with `next/image`
-- Instant global deployments by pushing to git
+- Instant global deployments via `git push`
 
 You can start using Vercel (for free) through a personal hobby account, or create a team to start the next big thing. Learn more about [Next.js on Vercel](https://vercel.com/solutions/nextjs) or read the [Vercel Documentation](https://vercel.com/docs).
 
@@ -82,7 +82,7 @@ Then, run `next build` to build your application. Finally, run `next start` to s
 Next.js can be deployed to any hosting provider that supports [Docker](https://www.docker.com/) containers. You can use this approach when deploying to container orchestrators such as [Kubernetes](https://kubernetes.io/) or [HashiCorp Nomad](https://www.nomadproject.io/), or when running inside a single node in any cloud provider.
 
 1. [Install Docker](https://docs.docker.com/get-docker/) on your machine
-1. [Use this example](https://github.com/vercel/next.js/tree/canary/examples/with-docker)
+1. Clone the [with-docker](https://github.com/vercel/next.js/tree/canary/examples/with-docker) example
 1. Build your container: `docker build -t nextjs-docker .`
 1. Run your container: `docker run -p 3000:3000 nextjs-docker`