correct build-auto-generated-files check names for fork PR failures

Author: melissag-ensemble

src/pages/deploy/index.md

@@ -263,9 +263,9 @@ After triggering a deployment:
 - Run the **Build Auto-Generated Files** workflow manually before deploying: Actions → Build Auto-Generated Files → Run workflow
 - See [FAQ](../faq/index.md) for more details
 
-#### `build-auto-generated-files` Failing on a Fork PR
+#### `Build Contributors` or `Build Site Metadata` Check Failing on a Fork PR
 
-**Symptoms:** PRs opened from forks fail the `build-auto-generated-files` check
+**Symptoms:** PRs opened from forks fail the `Build Contributors / build-contributors` or `Build Site Metadata / build-site-metadata` check
 
 **Solutions:**
 - Run the **Build Auto-Generated Files** workflow manually and merge ignoring the failed check

src/pages/faq/index.md

@@ -55,9 +55,9 @@ Actions → Build Auto-Generated Files → Run workflow
 
 This is a known limitation tracked in [DEVSITE-2395](https://jira.corp.adobe.com/browse/DEVSITE-2395).
 
-## Why is `build-auto-generated-files` failing on a PR from a fork?
+## Why are the `Build Contributors` or `Build Site Metadata` checks failing on a PR from a fork?
 
-PRs opened from forks will fail the `build-auto-generated-files` check. This was fixed in v2 workflows, but existing repos are still on v1 and will be updated via the retro repo update process ([DEVSITE-2249](https://jira.corp.adobe.com/browse/DEVSITE-2249)).
+PRs opened from forks may fail the `Build Contributors / build-contributors` or `Build Site Metadata / build-site-metadata` checks. This was fixed in v2 workflows, but existing repos are still on v1 and will be updated via the retro repo update process ([DEVSITE-2249](https://jira.corp.adobe.com/browse/DEVSITE-2249)).
 
 Until your repo is updated to v2 workflows:
 1. Go to Actions → Build Auto-Generated Files → Run workflow and wait for it to complete