DOCS: Update Vercel provider docs (#3877)

Made a few mistakes when creating the initial version of the docs back
in #3542

Fix typos, adjust a few wordings, descriptions, etc.

Co-authored-by: Tom Limoncelli <6293917+tlimoncelli@users.noreply.github.com>

documentation/provider/vercel.md

@@ -19,17 +19,17 @@ Example:
 
 **API Token**
 
-You can create a Vercel API Token via [Vercel Account Settngs](https://vercel.com/account/settings/tokens).
+You can create a Vercel API Token via [Vercel Account Settings - Tokens](https://vercel.com/account/settings/tokens).
 
 **How to grab team ID**
 
 Log in to your Vercel account and navigate to `https://vercel.com`. Switch to your desired team with the Vercel team switcher if needed.
 
-![Example permissions configuration](../assets/providers/vercel/vercel-account-switcher.png)
+![Vercel Team Switcher](../assets/providers/vercel/vercel-account-switcher.png)
 
-Now you can find your team ID in your browser's address bar, copy the path (**without** any leading `/` or trailing `/`) and paste it into your `creds.json` file.
+Now you can find your team ID in your browser's address bar, copy the path (**without** any leading `/` or trailing `/`) and paste it into your `creds.json` file's `team_id` field.
 
-![Example permissions configuration](../assets/providers/vercel/vercel-team-id-slug.png)
+![Vercel Team ID Slug in Browser Address Bar](../assets/providers/vercel/vercel-team-id-slug.png)
 
 If you are familiar with the Vercel API, you can also grab your team ID via Vercel's [Teams - List all teams API](https://vercel.com/docs/rest-api/reference/endpoints/teams/list-all-teams). In response's `id` field you will able to see a string starts with `team_`, and in response's `slug` field you will able to see a string consists of a slugified version of your team name. Both `id` and `slug` can be used as `team_id` for your `creds.json`.
 
@@ -50,7 +50,7 @@ In this case, you should use an empty string as the team ID:
 ```
 {% endcode %}
 
-It is also possible to manually migrate your domains from your Vercel account to your personal team via the link mentioned above. Whether you choose to migrate your domains or not is up to you, this provider supports both cases.
+It is possible to manually migrate your domains from your Vercel account to your personal team via the link mentioned above. Whether you choose to migrate your domains or not is up to you, this provider supports both scenarios.
 
 ## Usage
 
@@ -82,11 +82,11 @@ You can add your own records and Vercel will prefer your created records over th
 As of November 2025, the known system-managed records are:
 
 - `CAA 0 issue "letsencrypt.org"`
-  - Vercel uses Let's Encrypt to issue certificates for your project deployed on Vercel, thus Vercel automatically creates a CAA record to ensure Let's Encrypt can issue certificates, but you can always add your own CAA records.
+  - Vercel uses Let's Encrypt to issue certificates for your project deployed on Vercel, thus Vercel automatically creates a CAA record to ensure Let's Encrypt can issue certificates, but you can always add your own CAA records (you can even add your own `letsencrypt.org` CAA record and Vercel will dedupe that).
 - `CNAME cname.vercel-dns.com.`
-  - Vercel uses a CNAME record to point your deployed project to their infrastructure, but you can always add your own CNAME records (which allows you to put a third-party CDN in front of Vercel's infrastructure).
+  - Vercel always add a CNAME record to point your deployed project to their infrastructure, but you can always add your own A/AAAA/ALIAS/CNAME records (which allows you to put a third-party CDN in front of Vercel's infrastructure), and Vercel will always prefer your records over their default CNAME.
 
-In Vercel's API, those system-managed records will have their `creator` set to `system`. We use this to identify and ignore system-managed records, to prevent DNSControl from interfering with them. You won't see them in `dnscontrol diff` or `dnscontrol preview`.
+In Vercel's API, those system-managed records will have their `creator` set to `system`. We use this to identify and ignore system-managed records, to prevent DNSControl from interfering with them. You won't see them in `dnscontrol preview` or `dnscontrol get-zone`.
 
 ### Comment
 
@@ -99,7 +99,7 @@ In the future, we might use the comment field to store additional metadata for o
 As of November 2025, Vercel has a bug that does not accept CAA records with any extra fields that are not `cansigncansignhttpexchanges`:
 
 ```
-# OK  
+# OK
 CAA 0 issue "letsencrypt.org"
 CAA 0 issuewild "letsencrypt.org"
 CAA 0 issue "digicert.com; cansignhttpexchanges=yes"
@@ -135,10 +135,12 @@ We will burst through half of the quota, and then it spreads the requests evenly
 
 If you are mass migrating your DNS records from another provider to Vercel, we recommended to upload a BIND zone file via [Vercel's DNS Dashboard](https://vercel.com/dashboard/domains). You can use DNSControl to manage your DNS records afterwards.
 
+> This provider does not utilize that feature, as "upload a BIND zone file" is not documented and is not part of Vercel's public API.
+
 ### Change Record Type
 
 Vercel does not allow the record type to be changed after creation. If you try to update a record with a different type (e.g. changing `A` to `CNAME/ALIAS`), we will delete the old record and create a new one. This will count as two separate requests, which may exceed the rate limit. Also be careful about the downtime caused by the deletion and creation of records.
 
 ### Minimum TTL
 
-Vercel enforces a minimum TTL of 60 seconds (1 minute) for all records. We will always override the TTL to 60 seconds if you try to set a lower TTL.
+Vercel enforces a minimum TTL of 60 seconds (1 minute) for all records. We will always silently override the TTL to 60 seconds if you try to set a lower TTL.