docs: update vercel page

pi0 · pi0 · commit 2c9f8ea4a410 · 2025-07-15T12:49:03.000+02:00
diff --git a/docs/2.deploy/20.providers/vercel.md b/docs/2.deploy/20.providers/vercel.md
@@ -12,27 +12,23 @@ Integration with this provider is possible with [zero configuration](/deploy/#ze
 
 ## Deploy using git
 
-1. Push your code to your git repository (GitHub, GitLab, Bitbucket).
-2. [Import your project](https://vercel.com/new) into Vercel.
-3. Vercel will detect that you are using Nitro and will enable the correct settings for your deployment.
-4. Your application is deployed!
+
+- Push your code to your git repository (GitHub, GitLab, Bitbucket).
+- [Import your project](https://vercel.com/new) into Vercel.
+- Vercel will detect that you are using Nitro and will enable the correct settings for your deployment.
+- Your application is deployed!
+
 
 After your project has been imported and deployed, all subsequent pushes to branches will generate [Preview Deployments](https://vercel.com/docs/concepts/deployments/environments#preview), and all changes made to the Production Branch (commonly “main”) will result in a [Production Deployment](https://vercel.com/docs/concepts/deployments/environments#production).
 
 Learn more about Vercel’s [Git Integration](https://vercel.com/docs/concepts/git).
 
-## Monorepo
+## Monorepo support
 
 Monorepos are supported by Vercel. However a custom "[Root Directory](https://vercel.com/docs/deployments/configure-a-build#root-directory)" must be specified in "Project Settings > General" tab. Make sure that "Include source files outside of the Root Directory" is checked.
 
 Examples of values for "Root Directory": `apps/web` or `packages/app`.
 
-## API routes
-
-Nitro `/api` directory isn't compatible with Vercel. Instead, you should use:
-
-- `server/routes/api/` for standalone usage
-
 ## Custom build output configuration
 
 You can provide additional [build output configuration](https://vercel.com/docs/build-output-api/v3) using `vercel.config` key inside `nitro.config`. It will be merged with built-in auto-generated config.
@@ -43,10 +39,10 @@ On-demand revalidation allows you to purge the cache for an ISR route whenever y
 
 To revalidate a page on demand:
 
-1. Create an Environment Variable which will store a revalidation secret
+- Create an Environment Variable which will store a revalidation secret
     - You can use the command `openssl rand -base64 32` or [Generate a Secret](https://generate-secret.vercel.app/32) to generate a random value.
 
-2. Update your configuration:
+- Update your configuration:
 
     ::code-group
 
@@ -74,7 +70,7 @@ To revalidate a page on demand:
 
     ::
 
-3. To trigger "On-Demand Incremental Static Regeneration (ISR)" and revalidate a path to a Prerender Function, make a GET or HEAD request to that path with a header of x-prerender-revalidate: `bypassToken`. When that Prerender Function endpoint is accessed with this header set, the cache will be revalidated. The next request to that function should return a fresh response.
+- To trigger "On-Demand Incremental Static Regeneration (ISR)" and revalidate a path to a Prerender Function, make a GET or HEAD request to that path with a header of x-prerender-revalidate: `bypassToken`. When that Prerender Function endpoint is accessed with this header set, the cache will be revalidated. The next request to that function should return a fresh response.
 
 ### Fine-grained ISR config via route rules
 
