[Docs] Deprecated @now/next used in code example

[awareness481]

On Multi Zones we have this code example:

{
  "version": 2,
  "builds": [
    { "src": "blog/package.json", "use": "@now/next" },
    { "src": "home/package.json", "use": "@now/next" }
  ],
  "routes": [
    { "src": "/blog/_next(.*)", "dest": "blog/_next$1" },
    { "src": "/blog(.*)", "dest": "blog/blog$1" },
    { "src": "(.*)", "dest": "home$1" }
  ]
}

Visiting npm @now/next, it says that the package is deprecated and you should use @vercel/next instead. I've never used the multi-zones feature but I presume @vercel/next is correct here?

[mkamranhamid]

Hi I would like to work on it. But first let me pull the code to see if the example has the issue on my side as well

[mkamranhamid]

I don't see any errors as such just a warning and that is not related

WARNING: your application is being opted out of @vercel/next's optimized lambdas mode due to legacy routes in vercel.json. http://err.sh/vercel/vercel/next-legacy-routes-optimized-lambdas

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.