Added links in the config + deploy files

Author: D-K-P

docs/config/config-file.mdx

@@ -471,7 +471,7 @@ These environment variables are only used during the build process and are not e
 
 #### syncEnvVars
 
-The `syncEnvVars` build extension replaces the deprecated `resolveEnvVars` export. Check out our [syncEnvVars documentation](/deploy-environment-variables#sync-env-vars-from-another-service) for more information.
+The `syncEnvVars` build extension replaces the deprecated `resolveEnvVars` export. Check out our [syncEnvVars documentation](/deploy-environment-variables#sync-env-vars-from-another-service) for more information and example usage (including syncing environment variables from Infisical and Vercel).
 
 #### audioWaveform
 

docs/deploy-environment-variables.mdx

@@ -123,6 +123,10 @@ export default defineConfig({
 });
 ```
 
+#### Syncing environment variables from Vercel
+
+Check out our [syncing environment variables from Vercel example](/guides/examples/vercel-sync-env-vars) to see how to automatically sync environment variables from your Vercel projects to Trigger.dev.
+
 #### Deploy
 
 When you run the [CLI deploy command](/cli-deploy) directly or using [GitHub Actions](/github-actions) it will sync the environment variables from [Infisical](https://infisical.com) to Trigger.dev. This means they'll appear on the Environment Variables page so you can confirm that it's worked.