Update docs-team cross-repo references to technical-content

.github/instructions/instruction-architecture.instructions.md

@@ -8,6 +8,6 @@ This applies when you add, edit, or remove a Copilot instruction or shared agent
 
 When it applies, you **must** first read the instruction-architecture doc in full and follow it:
 
-https://github.com/github/docs-team/blob/main/contributing-to-docs/docs-work/copilot-instruction-architecture.md
+https://github.com/github/technical-content/blob/main/contributing-to-docs/docs-work/copilot-instruction-architecture.md
 
-Read the current version every time (from a local `github/docs-team` checkout if you have one, otherwise fetch the URL); do not rely on your memory of it, because it changes. If you cannot access it, say so and stop rather than guessing.
+Read the current version every time (from a local `github/technical-content` checkout if you have one, otherwise fetch the URL); do not rely on your memory of it, because it changes. If you cannot access it, say so and stop rather than guessing.

.github/workflows/review-comment.yml

@@ -97,6 +97,6 @@ jobs:
             🤖 This comment is [automatically generated][workflow].
 
             [workflow]: ${{ github.server_url }}/${{ github.repository }}/blob/${{ github.workflow_sha }}/.github/workflows/review-comment.yml
-            [codespace]: ${{ github.repository == 'github/docs-internal' && 'https://github.com/github/docs-team/blob/main/contributing-to-docs/tips-and-tricks/use-a-codespace-to-review.md' || 'https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace' }}
+            [codespace]: ${{ github.repository == 'github/docs-internal' && 'https://github.com/github/technical-content/blob/main/contributing-to-docs/tips-and-tricks/use-a-codespace-to-review.md' || 'https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace' }}
             [local]: https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment#setting-up-your-local-environment
-            [staging]: https://github.com/github/docs-team/blob/main/contributing-to-docs/tips-and-tricks/deploying-pr-to-staging-servers.md
+            [staging]: https://github.com/github/technical-content/blob/main/contributing-to-docs/tips-and-tricks/deploying-pr-to-staging-servers.md

.github/workflows/sme-review-tracking-issue.yml

@@ -31,10 +31,10 @@ jobs:
 
             const issueNo = context.number || context.issue.number
 
-            // Create an issue in docs-team repo
+            // Create an issue in technical-content repo
             await github.rest.issues.create({
               owner: 'github',
-              repo: 'docs-team',
+              repo: 'technical-content',
               title: `SME tracking issue for \#${issueNo}`,
               body: `### Issue / PR that requires an SME review
 

.github/workflows/sync-openapi.yml

@@ -102,7 +102,7 @@ jobs:
             --title "Update OpenAPI Description" \
             --body '👋 humans. This PR updates the OpenAPI description with the latest changes. (Synced from github/rest-api-description@${{ steps.rest-api-description.outputs.OPENAPI_COMMIT_SHA }})
 
-            Docs First Responders should follow [the acting-as-the-first-responder instructions](https://github.com/github/docs-team/blob/main/contributing-to-docs/first-responder/acting-as-the-first-responder.md?plain=1#L156).
+            Docs First Responders should follow [the acting-as-the-first-responder instructions](https://github.com/github/technical-content/blob/main/contributing-to-docs/first-responder/acting-as-the-first-responder.md?plain=1#L156).
 
             If CI does not pass or other problems arise, contact #docs-engineering on slack.
 

data/variables/release-phases.yml

@@ -1,5 +1,5 @@
 # Contains variables to identify GitHub's release phases. These are aligned with Microsoft standards.
-# For reference: https://github.com/github/docs-team/issues/4302
+# For reference: https://github.com/github/technical-content/issues/4302
 
 preview: 'preview'
 

src/events/components/experiments/content-ab-testing.md

@@ -2,7 +2,7 @@
 
 This guide explains how to set up an A/B test on article content using the experiment framework. Both content variants live in the same Markdown file and are served in a single Fastly-cached response. Client-side JavaScript swaps which variant is visible based on the user's experiment group.
 
-For background on A/B testing at GitHub Docs, see [the A/B testing guide](https://github.com/github/docs-team/blob/main/analytics/ab-test.md).
+For background on A/B testing at GitHub Docs, see [the A/B testing guide](https://github.com/github/technical-content/blob/main/analytics/ab-test.md).
 
 > [!IMPORTANT]
 > Only one experiment can have `includeVariationInContext: true` at a time, because `experiment_variation` is a single key in the event context. Multiple experiments can run concurrently if the others use `sendExperimentSuccess` for tracking instead. See the [experiments README](./README.md) for details.
@@ -65,7 +65,7 @@ To analyze additional event types (such as scroll depth or time on page), add qu
 
 Use the **[Docs Experiment Results dashboard](https://gh.io/docs-8c0c)** to track split verification, CTA click-through rates, sequential significance testing, and per-article breakdowns. The dashboard has parameters for experiment name, path product, and minimum detectable effect.
 
-Dashboard source config: [`docs-team/analytics/dashboard-builder/experiment-results.config.ts`](https://github.com/github/docs-team/blob/main/analytics/dashboard-builder/experiment-results.config.ts)
+Dashboard source config: [`technical-content/analytics/dashboard-builder/experiment-results.config.ts`](https://github.com/github/technical-content/blob/main/analytics/dashboard-builder/experiment-results.config.ts)
 
 ## Ending the experiment
 

src/ghes-releases/lib/release-templates/release-steps-0.md

@@ -91,8 +91,8 @@ Optionally, use and update the following table to keep track of key deadlines.
 * Slides
   * `TBD`
 * Docs
-  * [Creating a GitHub Enterprise Server instance](https://github.com/github/docs-team/blob/main/contributing-to-docs/docs-work/creating-a-github-enterprise-server-instance.md) in `github/docs-team`
-    * [Internal builds](https://github.com/github/docs-team/blob/main/contributing-to-docs/docs-work/creating-a-github-enterprise-server-instance.md#internal-builds), for testing pre-release RC builds
+  * [Creating a GitHub Enterprise Server instance](https://github.com/github/technical-content/blob/main/contributing-to-docs/docs-work/creating-a-github-enterprise-server-instance.md) in `github/technical-content`
+    * [Internal builds](https://github.com/github/technical-content/blob/main/contributing-to-docs/docs-work/creating-a-github-enterprise-server-instance.md#internal-builds), for testing pre-release RC builds
 * Slack
   * #tmp-docs-ghes-3-1x
   * [#docs-driver-persona](https://github-grid.enterprise.slack.com/archives/C07KVNQ6AVA)

src/redirects/lib/version-preference.ts

@@ -48,7 +48,7 @@ const NOTHING: VersionPreference = { vary: false }
 /**
  * Work out whether a reader's version preference applies to a request.
  *
- * The rule, decided in github/docs-team#7227, is that version behaves exactly like
+ * The rule, decided in github/technical-content#7227, is that version behaves exactly like
  * language: the cookie is only a default, a version named in the URL always wins, and
  * an article that does not exist in the preferred version silently stays where it is.
  *

src/redirects/middleware/handle-redirects.ts

@@ -141,7 +141,7 @@ export default function handleRedirects(req: ExtendedRequest, res: Response, nex
   //
   // Without this, the cookie is only ever consulted on the bare homepage, so a deep link
   // from search, the product UI, or a bookmark silently serves Free/Pro/Team. See
-  // github/docs-team#7227 for the measurements.
+  // github/technical-content#7227 for the measurements.
   //
   // This is deliberately its own branch rather than a tweak to `redirect` below, because
   // the ordinary path would emit a 301 for a language-prefixed URL. A redirect that

src/versions/tests/version-cookie.ts

@@ -58,7 +58,7 @@ describe('version cookie redirects', () => {
   })
 })
 
-// See github/docs-team#7227. Before this, the cookie was only ever consulted on the bare
+// See github/technical-content#7227. Before this, the cookie was only ever consulted on the bare
 // homepage, so every deep link served Free/Pro/Team no matter what the reader preferred.
 describe('version cookie on article URLs', () => {
   // Exists in Free/Pro/Team and in Enterprise Cloud.

src/workflows/measure-instruction-budget.ts

@@ -26,8 +26,8 @@ import { encode } from 'gpt-tokenizer/encoding/o200k_base'
 import readFrontmatter from '@/frame/lib/read-frontmatter'
 
 // Single source of truth for the guardrails. Keep these in sync with the
-// instruction architecture doc (github/docs-team) and any future CI check.
-// Derived in github/docs-team#6829: frontier models stay near-perfect to
+// instruction architecture doc (github/technical-content) and any future CI check.
+// Derived in github/technical-content#6829: frontier models stay near-perfect to
 // ~150 discrete instructions; ~45 tokens/rule puts the token backstop at ~6,500.
 const RULE_BUDGET = 150
 const TOKEN_BUDGET = 6500