docs(migrations): remove duplicated article

Remove the repeated 'the' from the cross-repository link example so the migration guidance reads correctly. Changes: - content/migrations/elm/migrated-data-reference.md - Correct the duplicated article in the link-rewriting example. Validation: - npm run lint-content -- --paths content/migrations/elm/migrated-data-reference.md - git diff --check
subatoi · Aug 13, 2026 · Aug 12, 2026 · Aug 12, 2026 · Aug 12, 2026 · Aug 12, 2026
commit fcd1b974ba00efde4ed768cdf2c7274ae9015d3e
diff --git a/content/migrations/elm/migrated-data-reference.md b/content/migrations/elm/migrated-data-reference.md
@@ -154,4 +154,4 @@ The following are exported during initial backfill only and are **not** updated
 
 References **within the source repository**, such as user mentions or links to issues and pull requests in the same repository, are rewritten so that they will still point to the correct resources after migration.
 
-References to **different repositories** (such as a link to an issue in the the `repo-2` repository from a pull request in `repo-1`) are **not** migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.
+References to **different repositories** (such as a link to an issue in the `repo-2` repository from a pull request in `repo-1`) are **not** migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -154,4 +154,4 @@ The following are exported during initial backfill only and are not updated

		References within the source repository, such as user mentions or links to issues and pull requests in the same repository, are rewritten so that they will still point to the correct resources after migration.

		References to different repositories (such as a link to an issue in the the `repo-2` repository from a pull request in `repo-1`) are not migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.
		References to different repositories (such as a link to an issue in the `repo-2` repository from a pull request in `repo-1`) are not migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.