diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 4c6ff3c4fd..f54c51ee4e 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -11,7 +11,6 @@
 /script/ @github/docs-engineering
 /includes/ @github/docs-engineering
 /lib/search/popular-pages.json @github/docs-engineering
-app.json @github/docs-engineering
 Dockerfile @github/docs-engineering
 package-lock.json @github/docs-engineering
 package.json @github/docs-engineering
diff --git a/.github/actions-scripts/prod-deploy.js b/.github/actions-scripts/prod-deploy.js
deleted file mode 100755
index 387e1397be..0000000000
--- a/.github/actions-scripts/prod-deploy.js
+++ /dev/null
@@ -1,51 +0,0 @@
-#!/usr/bin/env node
-
-import getOctokit from '../../script/helpers/github.js'
-import deployToProduction from '../../script/deployment/deploy-to-production.js'
-
-const {
-  GITHUB_TOKEN,
-  HEROKU_API_TOKEN,
-  HEROKU_PRODUCTION_APP_NAME,
-  SOURCE_BLOB_URL,
-  DELAY_FOR_PREBOOT,
-  RUN_ID,
-} = process.env
-
-// Exit if GitHub Actions PAT is not found
-if (!GITHUB_TOKEN) {
-  throw new Error('You must supply a GITHUB_TOKEN environment variable!')
-}
-
-// Exit if Heroku API token is not found
-if (!HEROKU_API_TOKEN) {
-  throw new Error('You must supply a HEROKU_API_TOKEN environment variable!')
-}
-
-// Exit if Heroku App name is not found
-if (!HEROKU_PRODUCTION_APP_NAME) {
-  throw new Error('You must supply a HEROKU_PRODUCTION_APP_NAME environment variable!')
-}
-
-if (!RUN_ID) {
-  throw new Error('$RUN_ID not set')
-}
-
-// This helper uses the `GITHUB_TOKEN` implicitly!
-// We're using our usual version of Octokit vs. the provided `github`
-// instance to avoid versioning discrepancies.
-const octokit = getOctokit()
-
-try {
-  await deployToProduction({
-    octokit,
-    includeDelayForPreboot: DELAY_FOR_PREBOOT !== 'false',
-    // These parameters will ONLY be set by Actions
-    sourceBlobUrl: SOURCE_BLOB_URL,
-    runId: RUN_ID,
-  })
-} catch (error) {
-  console.error(`Failed to deploy to production: ${error.message}`)
-  console.error(error)
-  throw error
-}
diff --git a/.github/actions-scripts/staging-commit-status-success.js b/.github/actions-scripts/staging-commit-status-success.js
deleted file mode 100755
index e7e1a6ba97..0000000000
--- a/.github/actions-scripts/staging-commit-status-success.js
+++ /dev/null
@@ -1,42 +0,0 @@
-#!/usr/bin/env node
-
-import * as github from '@actions/github'
-
-import getOctokit from '../../script/helpers/github.js'
-
-const { GITHUB_TOKEN } = process.env
-
-// Exit if GitHub Actions PAT is not found
-if (!GITHUB_TOKEN) {
-  throw new Error('You must supply a GITHUB_TOKEN environment variable!')
-}
-
-// This helper uses the `GITHUB_TOKEN` implicitly!
-// We're using our usual version of Octokit vs. the provided `github`
-// instance to avoid versioning discrepancies.
-const octokit = getOctokit()
-
-const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env
-if (!CONTEXT_NAME) {
-  throw new Error('$CONTEXT_NAME not set')
-}
-if (!ACTIONS_RUN_LOG) {
-  throw new Error('$ACTIONS_RUN_LOG not set')
-}
-if (!HEAD_SHA) {
-  throw new Error('$HEAD_SHA not set')
-}
-
-const { context } = github
-const owner = context.repo.owner
-const repo = context.payload.repository.name
-
-await octokit.repos.createCommitStatus({
-  owner,
-  repo,
-  sha: HEAD_SHA,
-  context: CONTEXT_NAME,
-  state: 'success',
-  description: 'Successfully deployed! See logs.',
-  target_url: ACTIONS_RUN_LOG,
-})
diff --git a/.github/actions-scripts/staging-deploy.js b/.github/actions-scripts/staging-deploy.js
deleted file mode 100755
index 26dadc4157..0000000000
--- a/.github/actions-scripts/staging-deploy.js
+++ /dev/null
@@ -1,55 +0,0 @@
-#!/usr/bin/env node
-
-import parsePrUrl from '../../script/deployment/parse-pr-url.js'
-import getOctokit from '../../script/helpers/github.js'
-import deployToStaging from '../../script/deployment/deploy-to-staging.js'
-
-const { GITHUB_TOKEN, HEROKU_API_TOKEN } = process.env
-
-// Exit if GitHub Actions PAT is not found
-if (!GITHUB_TOKEN) {
-  throw new Error('You must supply a GITHUB_TOKEN environment variable!')
-}
-
-// Exit if Heroku API token is not found
-if (!HEROKU_API_TOKEN) {
-  throw new Error('You must supply a HEROKU_API_TOKEN environment variable!')
-}
-
-// This helper uses the `GITHUB_TOKEN` implicitly!
-// We're using our usual version of Octokit vs. the provided `github`
-// instance to avoid versioning discrepancies.
-const octokit = getOctokit()
-
-const { RUN_ID, PR_URL, SOURCE_BLOB_URL } = process.env
-if (!RUN_ID) {
-  throw new Error('$RUN_ID not set')
-}
-if (!PR_URL) {
-  throw new Error('$PR_URL not set')
-}
-if (!SOURCE_BLOB_URL) {
-  throw new Error('$SOURCE_BLOB_URL not set')
-}
-
-const { owner, repo, pullNumber } = parsePrUrl(PR_URL)
-if (!owner || !repo || !pullNumber) {
-  throw new Error(
-    `'pullRequestUrl' input must match URL format 'https://github.com/github/(docs|docs-internal)/pull/123' but was '${PR_URL}'`
-  )
-}
-
-const { data: pullRequest } = await octokit.pulls.get({
-  owner,
-  repo,
-  pull_number: pullNumber,
-})
-
-await deployToStaging({
-  octokit,
-  pullRequest,
-  forceRebuild: false,
-  // These parameters will ONLY be set by Actions
-  sourceBlobUrl: SOURCE_BLOB_URL,
-  runId: RUN_ID,
-})
diff --git a/.github/workflows/azure-preview-env-deploy.yml b/.github/workflows/azure-preview-env-deploy.yml
index f5cfb866e9..eb0d0ef153 100644
--- a/.github/workflows/azure-preview-env-deploy.yml
+++ b/.github/workflows/azure-preview-env-deploy.yml
@@ -157,6 +157,8 @@ jobs:
       - if: ${{ env.IS_PUBLIC_BUILD == 'true' }}
         name: Move acceptable user changes
         run: |
+          # Make sure recursive path expansion is enabled
+          shopt -s globstar
           rsync -rptovR ./user-code/content/./**/*.md ./content
           rsync -rptovR ./user-code/assets/./**/*.png ./assets
           rsync -rptovR ./user-code/data/./**/*.{yml,md} ./data
diff --git a/.github/workflows/hubber-contribution-help.yml b/.github/workflows/hubber-contribution-help.yml
index 8f84d851e8..7aa4d0d7f4 100644
--- a/.github/workflows/hubber-contribution-help.yml
+++ b/.github/workflows/hubber-contribution-help.yml
@@ -41,7 +41,7 @@ jobs:
         run: |
           gh pr comment $PR --body "Thanks so much for opening this PR and contributing to GitHub Docs!
 
-          - When you're ready for the Docs team to review this PR, apply the **ready-for-doc-review** label and your PR will be added to the [Docs Content review board](https://github.com/orgs/github/memexes/901?layout=table&groupedBy%5BcolumnId%5D=11024). **Please factor in at least 72 hours for a review, even longer if this is a substantial change.**
+          - When you're ready for the Docs team to review this PR, request a review by *docs-content* and your PR will be added to the [Docs Content review board](https://github.com/orgs/github/memexes/901?layout=table&groupedBy%5BcolumnId%5D=11024). **Please factor in at least 72 hours for a review, even longer if this is a substantial change.**
           - If this is a major update to the docs, you might want to go back and open an [issue](https://github.com/github/docs-content/issues/new/choose) to ensure we've covered all areas of the docs in these updates. Not doing so may result in delays or inaccurate documentation."
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/ping-staging-apps.yml b/.github/workflows/ping-staging-apps.yml
deleted file mode 100644
index b5654ff1e2..0000000000
--- a/.github/workflows/ping-staging-apps.yml
+++ /dev/null
@@ -1,31 +0,0 @@
-name: Ping staging apps
-
-# **What it does**: This keeps our staging applications from automatically spinning down.
-# **Why we have it**: Staging applications can hiberate without use.
-# **Who does it impact**: Anyone with a pull request in docs-internal.
-
-on:
-  schedule:
-    - cron: '10,30,50 * * * *' # every twenty minutes
-
-permissions:
-  contents: read
-
-jobs:
-  ping_staging_apps:
-    name: Ping
-    if: github.repository == 'github/docs-internal'
-    runs-on: ubuntu-latest
-    env:
-      HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-    steps:
-      - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-      - name: npm ci
-        run: npm ci
-      - name: Run script
-        run: script/ping-staging-apps.js
diff --git a/.github/workflows/prod-build-deploy.yml b/.github/workflows/prod-build-deploy.yml
deleted file mode 100644
index 31094bf7db..0000000000
--- a/.github/workflows/prod-build-deploy.yml
+++ /dev/null
@@ -1,199 +0,0 @@
-name: Production - Build and Deploy
-
-# **What it does**: Builds and deploys the default branch to production
-# **Why we have it**: To enable us to deploy the latest to production whenever necessary rather than relying on PR merges.
-# **Who does it impact**: All contributors.
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-permissions:
-  contents: read
-  deployments: write
-
-# This allows a subsequently queued workflow run to take priority over
-# previously queued runs but NOT interrupt currently executing runs
-concurrency:
-  group: '${{ github.workflow }}'
-  cancel-in-progress: false
-
-jobs:
-  build-and-deploy:
-    if: ${{ github.repository == 'github/docs-internal'}}
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    steps:
-      - name: Check out repo
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-        with:
-          persist-credentials: 'false'
-          lfs: 'true'
-
-      - name: Check out LFS objects
-        run: git lfs checkout
-
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      # Required for `npm pkg ...` command support
-      - name: Update to npm@^7.20.0
-        run: npm install --global npm@^7.20.0
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Clone early access
-        run: node script/early-access/clone-for-build.js
-        env:
-          DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-          GIT_BRANCH: main
-
-      - name: Cache nextjs build
-        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
-        with:
-          path: .next/cache
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
-
-      - name: Build
-        run: npm run build
-
-      - name: Remove development-only dependencies
-        run: npm prune --production
-
-      - name: Remove all npm scripts
-        run: npm pkg delete scripts
-
-      - name: Set npm script for Heroku build to noop
-        run: npm set-script heroku-postbuild "echo 'Application was pre-built!'"
-
-      - name: Create a gzipped archive
-        run: |
-          tar -cz --file=app.tar.gz \
-            node_modules/ \
-            .next/ \
-            assets/ \
-            content/ \
-            data/ \
-            includes/ \
-            lib/ \
-            middleware/ \
-            translations/ \
-            server.mjs \
-            package*.json \
-            .npmrc \
-            feature-flags.json \
-            next.config.js \
-            app.json \
-            Procfile
-
-      - name: Install the development dependencies again
-        run: npm install
-
-      - name: Create a Heroku build source
-        id: build-source
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-        with:
-          script: |
-            const { owner, repo } = context.repo
-
-            if (owner !== 'github') {
-              throw new Error(`Repository owner must be 'github' but was: ${owner}`)
-            }
-            if (repo !== 'docs-internal') {
-              throw new Error(`Repository name must be 'docs-internal' but was: ${repo}`)
-            }
-
-            const Heroku = require('heroku-client')
-            const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-
-            try {
-              const { source_blob: sourceBlob } = await heroku.post('/sources')
-              const { put_url: uploadUrl, get_url: downloadUrl } = sourceBlob
-
-              core.setOutput('upload_url', uploadUrl)
-              core.setOutput('download_url', downloadUrl)
-            } catch (error) {
-              if (error.statusCode === 503) {
-                console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/')
-              }
-              throw error
-            }
-
-      # See: https://devcenter.heroku.com/articles/build-and-release-using-the-api#sources-endpoint
-      - name: Upload to the Heroku build source
-        env:
-          UPLOAD_URL: ${{ steps.build-source.outputs.upload_url }}
-        run: |
-          curl "$UPLOAD_URL" \
-            -X PUT \
-            -H 'Content-Type:' \
-            --data-binary @app.tar.gz
-
-      - name: Deploy
-        id: deploy
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-          HEROKU_PRODUCTION_APP_NAME: ${{ secrets.HEROKU_PRODUCTION_APP_NAME }}
-          HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }}
-          HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }}
-          SOURCE_BLOB_URL: ${{ steps.build-source.outputs.download_url }}
-          DELAY_FOR_PREBOOT: 'true'
-          ALLOWED_POLLING_FAILURES_PER_PHASE: '15'
-          RUN_ID: ${{ github.run_id }}
-        run: .github/actions-scripts/prod-deploy.js
-
-      - name: Mark the deployment as inactive if timed out
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        if: ${{ steps.deploy.outcome == 'cancelled' }}
-        env:
-          DEPLOYMENT_ID: ${{ steps.deploy.outputs.deploymentId }}
-          LOG_URL: ${{ steps.deploy.outputs.logUrl }}
-        with:
-          script: |
-            const { DEPLOYMENT_ID, LOG_URL }  = process.env
-            const { owner, repo } = context.repo
-
-            if (!DEPLOYMENT_ID) {
-              throw new Error('A deployment wasn't created before a timeout occurred!')
-            }
-
-            await github.repos.createDeploymentStatus({
-              owner,
-              repo,
-              deployment_id: DEPLOYMENT_ID,
-              state: 'error',
-              description: 'The deployment step timed out. See workflow logs.',
-              log_url: LOG_URL,
-              // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-              // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-              // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-              mediaType: {
-                previews: ['ant-man', 'flash'],
-              },
-            })
-            console.log('⏲️ Deployment status: error - The deployment timed out...')
-
-      # - name: Purge Fastly edge cache
-      #   env:
-      #     FASTLY_TOKEN: ${{ secrets.FASTLY_TOKEN }}
-      #     FASTLY_SERVICE_ID: ${{ secrets.FASTLY_SERVICE_ID }}
-      #     FASTLY_SURROGATE_KEY: 'every-deployment'
-      #   run: .github/actions-scripts/purge-fastly-edge-cache.js
-
-      - name: Send Slack notification if workflow failed
-        uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340
-        if: ${{ failure() }}
-        with:
-          channel: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }}
-          bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }}
-          color: failure
-          text: Production deployment failed at commit ${{ github.sha }}. See https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}
diff --git a/.github/workflows/ready-for-doc-review.yml b/.github/workflows/ready-for-doc-review.yml
index 6959b98158..34a4c006fa 100644
--- a/.github/workflows/ready-for-doc-review.yml
+++ b/.github/workflows/ready-for-doc-review.yml
@@ -1,12 +1,12 @@
 name: Ready for docs-content review
 
-# **What it does**: Adds pull requests in the docs-internal repository to the docs-content review board when the "ready-for-doc-review" label is added
+# **What it does**: Adds pull requests in the docs-internal repository to the docs-content review board when the "ready-for-doc-review" label is added or when a review by docs-content is requested
 # **Why we have it**: So that other GitHub teams can easily request reviews from the docs-content team, and so that writers can see when a PR is ready for review
 # **Who does it impact**: Writers working in the docs-internal repository
 
 on:
   pull_request_target:
-    types: [labeled]
+    types: [labeled, review_requested]
 
 permissions:
   contents: read
@@ -14,7 +14,9 @@ permissions:
 jobs:
   request_doc_review:
     name: Request a review from the docs-content team
-    if: github.event.label.name == 'ready-for-doc-review' && github.repository == 'github/docs-internal'
+    if: >-
+      github.repository == 'github/docs-internal' &&
+      (github.event.label.name == 'ready-for-doc-review' || github.event.requested_team.name == 'docs-content')
     runs-on: ubuntu-latest
     steps:
       - name: Check out repo content
diff --git a/.github/workflows/remove-stale-staging-resources.yml b/.github/workflows/remove-stale-staging-resources.yml
deleted file mode 100644
index 5375869132..0000000000
--- a/.github/workflows/remove-stale-staging-resources.yml
+++ /dev/null
@@ -1,69 +0,0 @@
-name: Remove stale staging resources
-
-# **What it does**:
-# This cleans up any rogue staging applications and environments that outlasted
-# the closure of their corresponding pull requests.
-# **Why we have it**:
-# Staging applications and environments should be destroyed after their
-# corresponding pull request is closed or merged, especially to save money spent
-# on Heroku App staging deployments for closed PRs.
-# **Who does it impact**:
-# Anyone with a closed, spammy, or deleted pull request in docs or docs-internal.
-
-on:
-  schedule:
-    - cron: '15,45 * * * *' # every thirty minutes at :15 and :45
-
-permissions:
-  actions: read
-  contents: read
-  deployments: write
-  pull-requests: write
-
-jobs:
-  remove_stale_staging_apps:
-    name: Remove stale staging apps
-    if: ${{ github.repository == 'github/docs-internal' }}
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out repo's default branch
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-
-      - name: Setup Node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run script
-        run: script/remove-stale-staging-apps.js
-        env:
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-  remove_stale_staging_envs:
-    name: Remove stale staging environments
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out repo's default branch
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-
-      - name: Setup Node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run script
-        run: script/remove-stale-staging-envs.js
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          ELEVATED_TOKEN: ${{ secrets.DOCS_BOT_FR }}
-          REPO: ${{ github.repository }}
-          RUN_ID: ${{ github.run_id }}
diff --git a/.github/workflows/staging-build-and-deploy-pr.yml b/.github/workflows/staging-build-and-deploy-pr.yml
deleted file mode 100644
index 45db1bf149..0000000000
--- a/.github/workflows/staging-build-and-deploy-pr.yml
+++ /dev/null
@@ -1,210 +0,0 @@
-name: Staging - Build and Deploy PR (fast and private-only)
-
-# **What it does**: Builds and deploys PRs to staging but ONLY for docs-internal
-# **Why we have it**: Most PRs are made on the private repo. Let's make those extra fast if we can worry less about security.
-# **Who does it impact**: All staff.
-
-# This whole workflow is only guaranteed to be secure in the *private
-# repo* and because we repo-sync these files over the to the public one,
-# IT'S IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs-internal!
-
-on:
-  # The advantage of 'pull_request' over 'pull_request_target' is that we
-  # can make changes to this file and test them in a pull request, instead
-  # of relying on landing it in 'main' first.
-  # From a security point of view, its arguably safer this way because
-  # unlike 'pull_request_target', these only have secrets if the pull
-  # request creator has permission to access secrets.
-  pull_request:
-
-permissions:
-  actions: read
-  contents: read
-  deployments: write
-  pull-requests: read
-  statuses: write
-
-# This allows a subsequently queued workflow run to interrupt previous runs
-concurrency:
-  group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
-  cancel-in-progress: true
-
-jobs:
-  build-and-deploy-pr:
-    # Important. This whole file is only supposed to run in the PRIVATE repo.
-    if: ${{ github.repository == 'github/docs-internal' }}
-
-    # The assumption here is that self-hosted is faster (e.g CPU power)
-    # that the regular ones. And it matters in this workflow because
-    # we do heavy CPU stuff with `npm run build` and `tar`
-    # runs-on: ubuntu-latest
-    runs-on: self-hosted
-
-    timeout-minutes: 5
-
-    steps:
-      - name: Check out repo
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-        with:
-          lfs: 'true'
-          # To prevent issues with cloning early access content later
-          persist-credentials: 'false'
-
-      - name: Check out LFS objects
-        run: git lfs checkout
-
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Cache nextjs build
-        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
-        with:
-          path: .next/cache
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
-
-      - name: Build
-        run: npm run build
-
-      - name: Clone early access
-        run: node script/early-access/clone-for-build.js
-        env:
-          DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-          GIT_BRANCH: ${{ github.head_ref || github.ref }}
-
-      - name: Create a Heroku build source
-        id: build-source
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-        with:
-          script: |
-            const { owner, repo } = context.repo
-
-            if (owner !== 'github') {
-              throw new Error(`Repository owner must be 'github' but was: ${owner}`)
-            }
-            if (repo !== 'docs-internal') {
-              throw new Error(`Repository name must be 'docs-internal' but was: ${repo}`)
-            }
-
-            const Heroku = require('heroku-client')
-            const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-
-            try {
-              const { source_blob: sourceBlob } = await heroku.post('/sources')
-              const { put_url: uploadUrl, get_url: downloadUrl } = sourceBlob
-
-              core.setOutput('upload_url', uploadUrl)
-              core.setOutput('download_url', downloadUrl)
-            } catch (error) {
-              if (error.statusCode === 503) {
-                console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/')
-              }
-              throw error
-            }
-
-      - name: Remove development-only dependencies
-        run: npm prune --production
-
-      - name: Remove all npm scripts
-        run: npm pkg delete scripts
-
-      - name: Set npm script for Heroku build to noop
-        run: npm set-script heroku-postbuild "echo 'Application was pre-built!'"
-
-      - name: Delete heavy things we won't need deployed
-        run: |
-
-          # The dereferenced file is not used in runtime once the
-          # decorated file has been created from it.
-          rm -rf lib/rest/static/dereferenced
-
-          # Translations are never tested in Staging builds
-          # but let's keep the empty directory.
-          rm -rf translations
-          mkdir translations
-
-          # Delete all the big search indexes that are NOT English (`*-en-*`)
-          pushd lib/search/indexes
-          ls | grep -ve '\-en\b' | xargs rm
-          popd
-
-          # Note! Some day it would be nice to be able to delete
-          # all the heavy assets because they bloat the tarball.
-          # But it's not obvious how to test it then. For now, we'll have
-          # to accept that every staging build has a copy of the images.
-
-          # The assumption here is that a staging build will not
-          # need these legacy redirects. Only the redirects from
-          # front-matter will be at play.
-          # These static redirects json files are notoriously large
-          # and they make the tarball unnecessarily large.
-          echo '[]' > lib/redirects/static/archived-frontmatter-fallbacks.json
-          echo '{}' > lib/redirects/static/developer.json
-          echo '{}' > lib/redirects/static/archived-redirects-from-213-to-217.json
-
-          # This will turn every `lib/**/static/*.json` into
-          # an equivalent `lib/**/static/*.json.br` file.
-          # Once the server starts, it'll know to fall back to reading
-          # the `.br` equivalent if the `.json` file isn't present.
-          node .github/actions-scripts/compress-large-files.js
-
-      - name: Make the tarball for Heroku
-        run: |
-          # We can't delete the .next/cache directory from the workflow
-          # because it's needed for caching, but we can at least exclude it
-          # from the tarball. Then it can be cached but not weigh down the
-          # tarball we intend to deploy.
-          tar -zc --exclude=.next/cache --file=app.tar.gz \
-            node_modules/ \
-            .next/ \
-            assets/ \
-            content/ \
-            data/ \
-            includes/ \
-            lib/ \
-            middleware/ \
-            translations/ \
-            server.mjs \
-            package*.json \
-            .npmrc \
-            feature-flags.json \
-            next.config.js \
-            app.json \
-            Procfile
-
-          du -sh app.tar.gz
-
-      # See: https://devcenter.heroku.com/articles/build-and-release-using-the-api#sources-endpoint
-      - name: Upload to the Heroku build source
-        env:
-          UPLOAD_URL: ${{ steps.build-source.outputs.upload_url }}
-        run: |
-          curl "$UPLOAD_URL" \
-            -X PUT \
-            -H 'Content-Type:' \
-            --data-binary @app.tar.gz
-
-      # 'npm install' is faster than 'npm ci' because it only needs to
-      # *append* what's missing from ./node_modules/
-      - name: Re-install dependencies so we get devDependencies back
-        run: npm install --no-audit --no-fund --only=dev
-
-      - name: Deploy
-        id: deploy
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-          HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }}
-          HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }}
-          PR_URL: ${{ github.event.pull_request.html_url }}
-          SOURCE_BLOB_URL: ${{ steps.build-source.outputs.download_url }}
-          ALLOWED_POLLING_FAILURES_PER_PHASE: '15'
-          RUN_ID: ${{ github.run_id }}
-        run: .github/actions-scripts/staging-deploy.js
diff --git a/.github/workflows/staging-build-pr.yml b/.github/workflows/staging-build-pr.yml
deleted file mode 100644
index 91c54cc037..0000000000
--- a/.github/workflows/staging-build-pr.yml
+++ /dev/null
@@ -1,135 +0,0 @@
-name: Staging - Build PR
-
-# **What it does**: Builds PRs before deploying them.
-# **Why we have it**: Because it's not safe to share our deploy secrets with forked repos: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
-# **Who does it impact**: All contributors.
-
-# IT'S CRUCIALLY IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs!
-
-on:
-  pull_request:
-
-permissions:
-  contents: read
-
-# This allows a subsequently queued workflow run to interrupt previous runs
-# These are different from the concurrency in that here it checks if the
-# whole workflow runs again. The "inner concurrency" is used for
-# undeployments to cleaning up resources.
-concurrency:
-  group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
-  cancel-in-progress: true
-
-jobs:
-  build-pr:
-    # Important. This whole file is only supposed to run in the PUBLIC repo.
-    if: ${{ github.repository == 'github/docs' }}
-
-    runs-on: ${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }}
-    timeout-minutes: 5
-    # This interrupts Build and Deploy workflow runs in progress for this PR branch.
-    concurrency:
-      group: 'PR Staging @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
-      cancel-in-progress: true
-    steps:
-      - name: Check out repo
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-
-      # Make sure only approved files are changed if it's in github/docs
-      - name: Check changed files
-        if: ${{ github.event.pull_request.user.login != 'Octomerger' }}
-        uses: dorny/paths-filter@eb75a1edc117d3756a18ef89958ee59f9500ba58
-        id: filter
-        with:
-          # Base branch used to get changed files
-          base: 'main'
-
-          # Enables setting an output in the format in `${FILTER_NAME}_files
-          # with the names of the matching files formatted as JSON array
-          list-files: json
-
-          # Returns list of changed files matching each filter
-          filters: |
-            notAllowed:
-              - '*.js'
-              - '*.mjs'
-              - '*.cjs'
-              - '*.ts'
-              - '*.tsx'
-              - '*.json'
-              - '.npmrc'
-              - '.babelrc*'
-              - '.env*'
-              - 'script/**'
-              - 'Procfile'
-
-      # When there are changes to files we can't accept
-      - name: Fail when disallowed files are changed
-        if: ${{ steps.filter.outputs.notAllowed == 'true' }}
-        run: exit 1
-
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      # Required for `npm pkg ...` command support
-      - name: Update to npm@^7.20.0
-        run: npm install --global npm@^7.20.0
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Cache nextjs build
-        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
-        with:
-          path: .next/cache
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
-
-      - name: Build
-        run: npm run build
-
-      - name: Remove development-only dependencies
-        run: npm prune --production
-
-      - name: Remove all npm scripts
-        run: npm pkg delete scripts
-
-      - name: Set npm script for Heroku build to noop
-        run: npm set-script heroku-postbuild "echo 'Application was pre-built!'"
-
-      - name: Create an archive
-        run: |
-          tar -c --file=app.tar \
-            node_modules/ \
-            .next/ \
-            assets/ \
-            content/ \
-            data/ \
-            includes/ \
-            lib/ \
-            middleware/ \
-            translations/ \
-            server.mjs \
-            package*.json \
-            .npmrc \
-            feature-flags.json \
-            next.config.js \
-            app.json \
-            Procfile
-
-          # We can't delete the .next/cache directory from the workflow
-          # because it's needed for caching, but we can at least delete it
-          # from within the tarball. Then it can be cached but not
-          # weigh down the tarball we intend to deploy.
-          tar --delete --file=app.tar .next/cache
-
-      # Upload only the files needed to run this application.
-      # We are not willing to trust the rest (e.g. script/) for the remainder
-      # of the deployment process.
-      - name: Upload build artifact
-        uses: actions/upload-artifact@82c141cc518b40d92cc801eee768e7aafc9c2fa2
-        with:
-          name: pr_build
-          path: app.tar
diff --git a/.github/workflows/staging-deploy-pr.yml b/.github/workflows/staging-deploy-pr.yml
deleted file mode 100644
index 52c382a675..0000000000
--- a/.github/workflows/staging-deploy-pr.yml
+++ /dev/null
@@ -1,466 +0,0 @@
-name: Staging - Deploy PR
-
-# **What it does**: To deploy PRs to a Heroku staging environment.
-# **Why we have it**: To deploy with high visibility in case of failures.
-# **Who does it impact**: All contributors.
-
-# IT'S CRUCIALLY IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs!
-
-on:
-  workflow_run:
-    workflows:
-      - 'Staging - Build PR'
-    types:
-      - completed
-
-permissions:
-  actions: read
-  contents: read
-  deployments: write
-  pull-requests: read
-  statuses: write
-
-# IMPORTANT: Intentionally OMIT a `concurrency` configuration from this workflow's
-# top-level as we do not have any guarantee of identifying values being available
-# within the `github.event` context for PRs from forked repos!
-#
-# The implication of this shortcoming is that we may have multiple workflow runs
-# of this running at the same time for different commits within the same PR.
-# However, once they reach the `concurrency` configurations deeper down within
-# this workflow's jobs, then we can expect concurrent short-circuiting to begin.
-
-env:
-  CONTEXT_NAME: '${{ github.workflow }} / deploy (${{ github.event.workflow_run.event }})'
-  ACTIONS_RUN_LOG: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}
-  BUILD_ACTIONS_RUN_ID: ${{ github.event.workflow_run.id }}
-  BUILD_ACTIONS_RUN_LOG: https://github.com/${{ github.repository }}/actions/runs/${{ github.event.workflow_run.id }}
-
-jobs:
-  pr-metadata:
-    # This is needed because the workflow we depend on
-    # (see on.workflow_run.workflows) might be running from pushes on
-    # main. That's because it needs to do that to popular the cache.
-    if: >-
-      ${{
-        github.repository == 'github/docs' &&
-        github.event.workflow_run.event == 'pull_request' &&
-        github.event.workflow_run.conclusion == 'success'
-      }}
-    runs-on: ubuntu-latest
-    outputs:
-      number: ${{ steps.pr.outputs.number }}
-      url: ${{ steps.pr.outputs.url }}
-      state: ${{ steps.pr.outputs.state }}
-      head_sha: ${{ steps.pr.outputs.head_sha }}
-      head_branch: ${{ steps.pr.outputs.head_branch }}
-      head_label: ${{ steps.pr.outputs.head_label }}
-      head_ref: ${{ steps.pr.outputs.head_ref }}
-    steps:
-      - name: Find the originating pull request
-        id: pr
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          BUILD_ACTIONS_RUN_ID: ${{ env.BUILD_ACTIONS_RUN_ID }}
-        with:
-          script: |
-
-            // Curious about what version of node you get
-            console.log('Node version:', process.version)
-
-            // In order to find out the PR info for a forked repo, we must query
-            // the API for more info based on the originating workflow run
-            const { BUILD_ACTIONS_RUN_ID } = process.env
-            const { owner, repo } = context.repo
-            const { data: run } = await github.actions.getWorkflowRun({
-              owner,
-              repo,
-              run_id: BUILD_ACTIONS_RUN_ID,
-            })
-
-            // Gather PR-identifying information from the workflow run
-            const {
-              head_branch: headBranch,
-              head_sha: headSha,
-              head_repository: {
-                owner: { login: prRepoOwner },
-                name: prRepoName
-              }
-            } = run
-
-            const prIsInternal = owner === prRepoOwner && repo === prRepoName
-            let headLabel = `${prRepoOwner}:${headBranch}`
-
-            // If the PR is external, prefix its head branch name with the
-            // forked repo owner's login and their fork repo name e.g.
-            // "octocat/my-fork:docs".  We need to include the fork repo
-            // name as well to account for an API issue (this will work fine
-            // if they don't have a different fork repo name).
-            if (!prIsInternal) {
-              headLabel = `${prRepoOwner}/${prRepoName}:${headBranch}`
-            }
-
-            // If the PR is external, prefix its head branch name with the
-            // forked repo owner's login, e.g. "octocat:docs"
-            const headRef = prIsInternal ? headBranch : headLabel
-
-            // Retrieve matching PRs (up to 30)
-            const { data: pulls } = await github.pulls.list({
-              owner,
-              repo,
-              head: headLabel,
-              sort: 'updated',
-              direction: 'desc',
-              per_page: 30
-            })
-
-            // Find the open PR, if any, otherwise choose the most recently updated
-            const targetPull = pulls.find(pr => pr.state === 'open') || pulls[0] || {}
-
-            const pullNumber = targetPull.number || 0
-            const pullUrl = targetPull.html_url || 'about:blank'
-            const pullState = targetPull.state || 'closed'
-
-            core.setOutput('number', pullNumber.toString())
-            core.setOutput('url', pullUrl)
-            core.setOutput('state', pullState)
-            core.setOutput('head_sha', headSha)
-            core.setOutput('head_branch', headBranch)
-            core.setOutput('head_label', headLabel)
-            core.setOutput('head_ref', headRef)
-
-  debug-originating-trigger:
-    needs: pr-metadata
-    runs-on: ubuntu-latest
-    steps:
-      - name: Dump info about the originating workflow run
-        env:
-          PR_NUMBER: ${{ needs.pr-metadata.outputs.number }}
-          PR_URL: ${{ needs.pr-metadata.outputs.url }}
-          PR_STATE: ${{ needs.pr-metadata.outputs.state }}
-          HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }}
-          HEAD_BRANCH: ${{ needs.pr-metadata.outputs.head_branch }}
-          HEAD_LABEL: ${{ needs.pr-metadata.outputs.head_label }}
-          HEAD_REF: ${{ needs.pr-metadata.outputs.head_ref }}
-          BUILD_ACTIONS_RUN_ID: ${{ env.BUILD_ACTIONS_RUN_ID }}
-          BUILD_ACTIONS_RUN_LOG: ${{ env.BUILD_ACTIONS_RUN_LOG }}
-        run: |
-          echo "Originating workflow info:"
-          echo " - PR_NUMBER = $PR_NUMBER"
-          echo " - PR_URL = $PR_URL"
-          echo " - PR_STATE = $PR_STATE"
-          echo " - HEAD_SHA = $HEAD_SHA"
-          echo " - HEAD_BRANCH = $HEAD_BRANCH"
-          echo " - HEAD_LABEL = $HEAD_LABEL"
-          echo " - HEAD_REF = $HEAD_REF"
-          echo " - BUILD_ACTIONS_RUN_ID = $BUILD_ACTIONS_RUN_ID"
-          echo " - BUILD_ACTIONS_RUN_LOG = $BUILD_ACTIONS_RUN_LOG"
-
-  notify-of-failed-builds:
-    needs: pr-metadata
-    if: >-
-      ${{
-        needs.pr-metadata.outputs.number != '0' &&
-        github.event.workflow_run.conclusion == 'failure'
-      }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 1
-    # Specifically omitting a concurrency group here in case the build was not
-    # successful BECAUSE a subsequent build already canceled it
-    steps:
-      - name: Verify build workflow run was not cancelled
-        id: check-workflow-run
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          BUILD_ACTIONS_RUN_ID: ${{ env.BUILD_ACTIONS_RUN_ID }}
-        with:
-          script: |
-            const { owner, repo } = context.repo
-            const { data: { jobs: buildJobs } } = await github.actions.listJobsForWorkflowRun({
-              owner,
-              repo,
-              run_id: process.env.BUILD_ACTIONS_RUN_ID,
-              filter: 'latest'
-            })
-            const wasCancelled = (
-              buildJobs.length > 0 &&
-              buildJobs.every(({ status, conclusion }) => {
-                return status === 'completed' && conclusion === 'cancelled'
-              })
-            )
-            core.setOutput('cancelled', wasCancelled.toString())
-
-      - if: ${{ steps.check-workflow-run.outputs.cancelled == 'false' }}
-        name: Send Slack notification if build workflow failed
-        uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340
-        with:
-          channel: ${{ secrets.DOCS_STAGING_DEPLOYMENT_FAILURES_SLACK_CHANNEL_ID }}
-          bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }}
-          color: failure
-          text: Staging build failed for PR ${{ needs.pr-metadata.outputs.url }} at commit ${{ needs.pr-metadata.outputs.head_sha }}. See ${{ env.BUILD_ACTIONS_RUN_LOG }}. This run was ${{ env.ACTIONS_RUN_LOG }}.
-
-  prepare-for-deploy:
-    needs: pr-metadata
-    if: ${{ needs.pr-metadata.outputs.state == 'open' }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    # This interrupts Build and Deploy workflow runs in progress for this PR branch.
-    concurrency:
-      group: 'PR Staging @ ${{ needs.pr-metadata.outputs.head_label }}'
-      cancel-in-progress: true
-    outputs:
-      source_blob_url: ${{ steps.build-source.outputs.download_url }}
-    steps:
-      - name: Create initial status
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          CONTEXT_NAME: ${{ env.CONTEXT_NAME }}
-          ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }}
-          HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }}
-        with:
-          script: |
-            const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env
-            const { owner, repo } = context.repo
-            await github.repos.createCommitStatus({
-              owner,
-              repo,
-              sha: HEAD_SHA,
-              context: CONTEXT_NAME,
-              state: 'pending',
-              description: 'The app is being deployed. See logs.',
-              target_url: ACTIONS_RUN_LOG
-            })
-
-      - name: Check out repo's default branch
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-        with:
-          # To prevent issues with cloning early access content later
-          persist-credentials: 'false'
-          lfs: 'true'
-
-      - name: Check out LFS objects
-        run: git lfs checkout
-
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      # Install any additional dependencies *before* downloading the build artifact
-      - name: Install Heroku client development-only dependency
-        run: npm install --no-save heroku-client
-
-      # Download the previously built "app.tar"
-      - name: Download build artifact
-        uses: dawidd6/action-download-artifact@af92a8455a59214b7b932932f2662fdefbd78126
-        with:
-          workflow: ${{ github.event.workflow_run.workflow_id }}
-          run_id: ${{ env.BUILD_ACTIONS_RUN_ID }}
-          name: pr_build
-          path: ${{ runner.temp }}
-
-      # gzip the app.tar to meet Heroku's expected format
-      - name: Create a gzipped archive (docs)
-        run: gzip -9 < "$RUNNER_TEMP/app.tar" > app.tar.gz
-
-      - name: Create a Heroku build source
-        id: build-source
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-        with:
-          script: |
-            const { owner, repo } = context.repo
-
-            if (owner !== 'github') {
-              throw new Error(`Repository owner must be 'github' but was: ${owner}`)
-            }
-            if (repo !== 'docs') {
-              throw new Error(`Repository name must be 'docs' but was: ${repo}`)
-            }
-
-            const Heroku = require('heroku-client')
-            const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-
-            try {
-              const { source_blob: sourceBlob } = await heroku.post('/sources')
-              const { put_url: uploadUrl, get_url: downloadUrl } = sourceBlob
-
-              core.setOutput('upload_url', uploadUrl)
-              core.setOutput('download_url', downloadUrl)
-            } catch (error) {
-              if (error.statusCode === 503) {
-                console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/')
-              }
-              throw error
-            }
-
-      # See: https://devcenter.heroku.com/articles/build-and-release-using-the-api#sources-endpoint
-      - name: Upload to the Heroku build source
-        env:
-          UPLOAD_URL: ${{ steps.build-source.outputs.upload_url }}
-        run: |
-          curl "$UPLOAD_URL" \
-            -X PUT \
-            -H 'Content-Type:' \
-            --data-binary @app.tar.gz
-
-      - name: Create failure status
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        if: ${{ failure() }}
-        env:
-          CONTEXT_NAME: ${{ env.CONTEXT_NAME }}
-          ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }}
-          HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }}
-        with:
-          script: |
-            const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env
-            const { owner, repo } = context.repo
-            await github.repos.createCommitStatus({
-              owner,
-              repo,
-              sha: HEAD_SHA,
-              context: CONTEXT_NAME,
-              state: 'error',
-              description: 'Failed to deploy. See logs.',
-              target_url: ACTIONS_RUN_LOG
-            })
-
-      - name: Send Slack notification if deployment preparation job failed
-        uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340
-        if: ${{ failure() }}
-        with:
-          channel: ${{ secrets.DOCS_STAGING_DEPLOYMENT_FAILURES_SLACK_CHANNEL_ID }}
-          bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }}
-          color: failure
-          text: Staging preparation failed for PR ${{ needs.pr-metadata.outputs.url }} at commit ${{ needs.pr-metadata.outputs.head_sha }}. See ${{ env.ACTIONS_RUN_LOG }}.
-
-  check-pr-before-deploy:
-    needs: [pr-metadata, prepare-for-deploy]
-    runs-on: ubuntu-latest
-    timeout-minutes: 1
-    # This interrupts Build and Deploy workflow runs in progress for this PR branch.
-    concurrency:
-      group: 'PR Staging @ ${{ needs.pr-metadata.outputs.head_label }}'
-      cancel-in-progress: true
-    outputs:
-      pull_request_state: ${{ steps.check-pr.outputs.state }}
-    steps:
-      - name: Check pull request state
-        id: check-pr
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        env:
-          PR_NUMBER: ${{ needs.pr-metadata.outputs.number }}
-        with:
-          script: |
-            const { owner, repo } = context.repo
-            const { data: pullRequest } = await github.pulls.get({
-              owner,
-              repo,
-              pull_number: process.env.PR_NUMBER
-            })
-            core.setOutput('state', pullRequest.state)
-
-  deploy:
-    needs: [pr-metadata, prepare-for-deploy, check-pr-before-deploy]
-    if: ${{ needs.check-pr-before-deploy.outputs.pull_request_state == 'open' }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    # This interrupts Build and Deploy workflow runs in progress for this PR branch.
-    concurrency:
-      group: 'PR Staging @ ${{ needs.pr-metadata.outputs.head_label }}'
-      cancel-in-progress: true
-    steps:
-      - name: Check out repo's default branch
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Deploy
-        id: deploy
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
-          HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }}
-          HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }}
-          PR_URL: ${{ needs.pr-metadata.outputs.url }}
-          SOURCE_BLOB_URL: ${{ needs.prepare-for-deploy.outputs.source_blob_url }}
-          ALLOWED_POLLING_FAILURES_PER_PHASE: '15'
-          RUN_ID: ${{ github.run_id }}
-        run: .github/actions-scripts/staging-deploy.js
-
-      - name: Create successful commit status
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          CONTEXT_NAME: ${{ env.CONTEXT_NAME }}
-          ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }}
-          HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }}
-        run: .github/actions-scripts/staging-commit-status-success.js
-
-      - name: Mark the deployment as inactive if timed out
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        if: ${{ steps.deploy.outcome == 'cancelled' }}
-        env:
-          DEPLOYMENT_ID: ${{ steps.deploy.outputs.deploymentId }}
-          LOG_URL: ${{ steps.deploy.outputs.logUrl }}
-        with:
-          script: |
-            const { DEPLOYMENT_ID, LOG_URL }  = process.env
-            const { owner, repo } = context.repo
-
-            if (!DEPLOYMENT_ID) {
-              throw new Error('A deployment wasn't created before a timeout occurred!')
-            }
-
-            await github.repos.createDeploymentStatus({
-              owner,
-              repo,
-              deployment_id: DEPLOYMENT_ID,
-              state: 'error',
-              description: 'The deployment step timed out. See workflow logs.',
-              log_url: LOG_URL,
-              // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-              // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-              // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-              mediaType: {
-                previews: ['ant-man', 'flash'],
-              },
-            })
-            console.log('⏲️ Deployment status: error - The deployment timed out...')
-
-      - name: Create failure status
-        uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d
-        if: ${{ failure() }}
-        env:
-          CONTEXT_NAME: ${{ env.CONTEXT_NAME }}
-          ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }}
-          HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }}
-        with:
-          script: |
-            const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env
-            const { owner, repo } = context.repo
-            await github.repos.createCommitStatus({
-              owner,
-              repo,
-              sha: HEAD_SHA,
-              context: CONTEXT_NAME,
-              state: 'error',
-              description: 'Failed to deploy. See logs.',
-              target_url: ACTIONS_RUN_LOG
-            })
-
-      - name: Send Slack notification if deployment job failed
-        uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340
-        if: ${{ failure() }}
-        with:
-          channel: ${{ secrets.DOCS_STAGING_DEPLOYMENT_FAILURES_SLACK_CHANNEL_ID }}
-          bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }}
-          color: failure
-          text: Staging deployment failed for PR ${{ needs.pr-metadata.outputs.url }} at commit ${{ needs.pr-metadata.outputs.head_sha }}. See ${{ env.ACTIONS_RUN_LOG }}.
diff --git a/.github/workflows/test-windows.yml b/.github/workflows/test-windows.yml
deleted file mode 100644
index 52d77dd42c..0000000000
--- a/.github/workflows/test-windows.yml
+++ /dev/null
@@ -1,76 +0,0 @@
-# NOTE: Changes to this file should also be applied to './test.yml'
-
-name: Node.js Tests - Windows
-
-# **What it does**: This runs our tests on Windows.
-# **Why we have it**: We want to support Windows contributors to docs.
-# **Who does it impact**: Anyone working on docs on a Windows device.
-
-on:
-  workflow_dispatch:
-  pull_request:
-  schedule:
-    - cron: '50 19 * * *' # once a day at 19:50 UTC / 11:50 PST
-
-permissions:
-  contents: read
-
-# This allows a subsequently queued workflow run to interrupt previous runs
-concurrency:
-  group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
-  cancel-in-progress: true
-
-jobs:
-  test:
-    runs-on: windows-latest
-    if: (github.event_name != 'pull_request') || (github.event_name == 'pull_request' && (contains(github.event.pull_request.labels.*.name, 'Windows') || contains(github.event.pull_request.labels.*.name, 'windows')))
-    timeout-minutes: 60
-    strategy:
-      fail-fast: false
-      matrix:
-        test-group:
-          [
-            content,
-            graphql,
-            meta,
-            rendering,
-            routing,
-            unit,
-            linting,
-            translations,
-          ]
-    steps:
-      - name: Check out repo
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-        with:
-          # Enables cloning the Early Access repo later with the relevant PAT
-          persist-credentials: 'false'
-
-      - name: Setup node
-        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
-        with:
-          node-version: 16.13.x
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Cache nextjs build
-        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
-        with:
-          path: .next/cache
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
-
-      - if: ${{ github.repository == 'github/docs-internal' }}
-        name: Clone early access
-        run: npm run heroku-postbuild
-        env:
-          DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-          GIT_BRANCH: ${{ github.head_ref || github.ref }}
-
-      - if: ${{ github.repository != 'github/docs-internal' }}
-        name: Run build script
-        run: npm run build
-
-      - name: Run tests
-        run: npm test -- tests/${{ matrix.test-group }}/
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index b080e73df7..1db6685fae 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -1,5 +1,3 @@
-# NOTE: Changes to this file should also be applied to './test-windows.yml'
-
 name: Node.js Tests
 
 # **What it does**: Runs our tests.
diff --git a/.github/workflows/triage-unallowed-contributions.yml b/.github/workflows/triage-unallowed-contributions.yml
index 0cb30cdd6f..caae155b4a 100644
--- a/.github/workflows/triage-unallowed-contributions.yml
+++ b/.github/workflows/triage-unallowed-contributions.yml
@@ -10,7 +10,6 @@ on:
       - '.github/actions-scripts/**'
       - '.github/workflows/**'
       - '.github/CODEOWNERS'
-      - 'app.json'
       - 'assets/fonts/**'
       - 'data/graphql/**'
       - 'Dockerfile*'
@@ -20,7 +19,6 @@ on:
       - 'lib/webhooks/**'
       - 'lib/search/indexes/**'
       - 'package*.json'
-      - 'Procfile'
       - 'script/**'
       - 'translations/**'
 
@@ -58,7 +56,6 @@ jobs:
               - '.github/actions-scripts/**'
               - '.github/workflows/**'
               - '.github/CODEOWNERS'
-              - 'app.json'
               - 'assets/fonts/**'
               - 'data/graphql/**'
               - 'Dockerfile*'
@@ -68,7 +65,6 @@ jobs:
               - 'lib/webhooks/**'
               - 'lib/search/indexes/**'
               - 'package*.json'
-              - 'Procfile'
               - 'scripts/**'
               - 'translations/**'
 
@@ -83,7 +79,6 @@ jobs:
               '.github/actions-scripts/**',
               '.github/workflows/**',
               '.github/CODEOWNERS',
-              'app.json',
               'assets/fonts/**',
               'data/graphql/**',
               'Dockerfile*',
@@ -93,7 +88,6 @@ jobs:
               'lib/webhooks/**',
               'lib/search/indexes/**',
               'package*.json',
-              'Procfile',
               'scripts/**',
               'translations/**',
             ]
@@ -111,7 +105,7 @@ jobs:
                 body: reviewMessage,
               })
 
-              workflowFailMessage = `${workflowFailMessage} Please see ${createdComment.data.html_url} for details.` 
+              workflowFailMessage = `${workflowFailMessage} Please see ${createdComment.data.html_url} for details.`
             } catch(err) {
               console.log("Error creating comment.", err)
             }
diff --git a/.github/workflows/triage-unallowed-internal-changes.yml b/.github/workflows/triage-unallowed-internal-changes.yml
index f839c016e9..4a505b2afc 100644
--- a/.github/workflows/triage-unallowed-internal-changes.yml
+++ b/.github/workflows/triage-unallowed-internal-changes.yml
@@ -1,7 +1,7 @@
 name: Check for unallowed internal changes
 
-# **What it does**: If someone changes app.json or search indexes, we fail the check.
-# **Why we have it**: app.json should rarely be edited, so we'll require an admin merge if the file really needs to be changed. The search indexes are synced every 4 hours, so changes should not need to be made.
+# **What it does**: If someone changes search indexes, we fail the check.
+# **Why we have it**: The search indexes are synced every 4 hours, so changes should not need to be made.
 # **Who does it impact**: Docs engineering and content writers.
 
 on:
@@ -44,19 +44,8 @@ jobs:
 
           # Returns list of changed files matching each filter
           filters: |
-            notAllowed:
-              - 'app.json'
             notAllowedSearchSyncLabel:
               - 'lib/search/indexes/**'
-  notAllowed:
-    needs: check-internal-changes
-    if: ${{ needs.check-internal-changes.outputs.notAllowed == 'true' }}
-    runs-on: ubuntu-latest
-    steps:
-      - name: Fail if unallowed changes were made
-        run: |
-          echo "Please admin merge if you really need to update app.json!"
-          exit 1
   notAllowedSearchSyncLabel:
     needs: check-internal-changes
     if: ${{ needs.check-internal-changes.outputs.notAllowedSearchSyncLabel == 'true' }}
diff --git a/Dockerfile b/Dockerfile
index 985bde3af7..cad07f06c9 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,6 +1,4 @@
-# This Dockerfile can be used for docker-based deployments to platforms
-# like Now or Moda, but it is currently _not_ used by our Heroku deployments
-# It uses two multi-stage builds: `install` and the main build to keep the image size down.
+# This Dockerfile is used for docker-based deployments to Azure for both preview environments and production
 
 # --------------------------------------------------------------------------------
 # BASE IMAGE
diff --git a/Procfile b/Procfile
deleted file mode 100644
index 4bec004287..0000000000
--- a/Procfile
+++ /dev/null
@@ -1 +0,0 @@
-web: NODE_ENV=production node server.mjs
diff --git a/app.json b/app.json
deleted file mode 100644
index 14f8ba9f54..0000000000
--- a/app.json
+++ /dev/null
@@ -1,17 +0,0 @@
-{
-  "name": "docs.github.com",
-  "env": {
-    "NODE_ENV": "production",
-    "ENABLED_LANGUAGES": "en",
-    "WEB_CONCURRENCY": "1"
-  },
-  "buildpacks": [
-    { "url": "heroku/nodejs" }
-  ],
-  "formation": {
-    "web": {
-      "quantity": 1,
-      "size": "standard-2x"
-    }
-  }
-}
diff --git a/assets/images/create_app.png b/assets/images/create_app.png
index 20f24d95f6..3a1dca57f8 100644
Binary files a/assets/images/create_app.png and b/assets/images/create_app.png differ
diff --git a/assets/images/deploy-key.png b/assets/images/deploy-key.png
index 2043f710cf..30d2b8c999 100644
Binary files a/assets/images/deploy-key.png and b/assets/images/deploy-key.png differ
diff --git a/assets/images/help/repository/headings_toc.png b/assets/images/help/repository/headings_toc.png
new file mode 100644
index 0000000000..9370750baf
Binary files /dev/null and b/assets/images/help/repository/headings_toc.png differ
diff --git a/assets/images/install_permissions.png b/assets/images/install_permissions.png
index 3ece4e3eb9..8540bcda46 100644
Binary files a/assets/images/install_permissions.png and b/assets/images/install_permissions.png differ
diff --git a/assets/images/private_key.png b/assets/images/private_key.png
index f5b0a2364b..ebc1c58e7c 100644
Binary files a/assets/images/private_key.png and b/assets/images/private_key.png differ
diff --git a/assets/images/settings/developer_settings.png b/assets/images/settings/developer_settings.png
index 455deba228..4eb1d920da 100644
Binary files a/assets/images/settings/developer_settings.png and b/assets/images/settings/developer_settings.png differ
diff --git a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index b40a64343b..671a5db72b 100644
--- a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -89,10 +89,14 @@ This procedure demonstrates how to create the service account for your GKE integ
   {% raw %}
   ```
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
-    --member=serviceAccount:$SA_EMAIL \
-    --role=roles/container.admin \
-    --role=roles/storage.admin \
-    --role=roles/container.clusterViewer
+  	--member=serviceAccount:$SA_EMAIL \
+  	--role=roles/container.admin
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+  	--member=serviceAccount:$SA_EMAIL \
+  	--role=roles/storage.admin
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+  	--member=serviceAccount:$SA_EMAIL \
+  	--role=roles/container.clusterViewer
   ```
   {% endraw %}
 1. Download the JSON keyfile for the service account:
diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md
index ffad10c4e1..bf23322ffd 100644
--- a/content/actions/learn-github-actions/contexts.md
+++ b/content/actions/learn-github-actions/contexts.md
@@ -76,7 +76,7 @@ The following table indicates where each context and special function can be use
 | <code>concurrency</code> | <code>github, inputs</code> | |
 | <code>env</code> | <code>github, secrets, inputs</code> | |
 | <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> | |
 | <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
 | <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
 | <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> | |
diff --git a/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index f3c3379e0b..440edcc597 100644
--- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -757,6 +757,8 @@ strategy:
 
 ## `jobs.<job_id>.container`
 
+{% data reusables.github-actions.docker-container-os-support %}
+
 {% data reusables.actions.jobs.section-running-jobs-in-a-container %}
 
 ### `jobs.<job_id>.container.image`
diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
index f3d8b48da6..689660934f 100644
--- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
+++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
@@ -98,7 +98,7 @@ shortTitle: Export from your enterprise
   > logout
   > Connection to <em>hostname</em> closed.
   ```
-9. Copy the migration archive to your computer using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID:
+9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID:
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:/data/github/current/tmp/<em>MIGRATION_GUID</em>.tar.gz ~/Desktop
   ```
diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index 12b0ae88e1..177d878409 100644
--- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -19,7 +19,7 @@ shortTitle: Prepare to migrate data
 ---
 ## Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
 
-1. Using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target:
+1. Using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target:
 
     ```shell
     $ scp -P 122 <em>/path/to/archive/MIGRATION_GUID.tar.gz</em> admin@<em>hostname</em>:/home/admin/
@@ -43,7 +43,7 @@ shortTitle: Prepare to migrate data
     $ ghe-migrator conflicts -g <em>MIGRATION_GUID</em> > conflicts.csv
     ```
     - If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
-2. If there are conflicts, using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer:
+2. If there are conflicts, using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer:
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:conflicts.csv ~/Desktop
   ```
@@ -133,7 +133,7 @@ The same process can be used to create mappings for each record that supports cu
 
 ### Applying modified migration data
 
-1. After making changes, use the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance:
+1. After making changes, use the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance:
 
     ```shell
     $ scp -P 122 ~/Desktop/conflicts.csv admin@<em>hostname</em>:/home/admin/
diff --git a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
index 480901f678..858faf9151 100644
--- a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
+++ b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
@@ -29,7 +29,7 @@ You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP add
 
 These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
 
-These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this  [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges.
+These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool to convert from CIDR notation to IP address ranges, for example: [CIDR to IPv4 conversion site](https://www.ipaddressguide.com/cidr).
 
 We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
 
diff --git a/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
index edf1015910..a23805bf67 100644
--- a/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
+++ b/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -60,4 +60,4 @@ For an example of an incident response workflow, see the "Data Breach Response P
 
 You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability.
 
-If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)."
+If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)."
diff --git a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 4956d47f3f..07bf02fa30 100644
--- a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -24,6 +24,11 @@ To create a heading, add one to six <kbd>#</kbd> symbols before your heading tex
 
 ![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png)
 
+When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section. 
+
+![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png)
+
+
 ## Styling text
 
 You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files.  
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index d6ac9ce97e..9112cf8d90 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -17,7 +17,7 @@ topics:
 ---
 People with admin or owner permissions can set up a CODEOWNERS file in a repository.
 
-The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
+The people you choose as code owners must have read permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
 
 ## About code owners
 
@@ -42,7 +42,7 @@ For code owners to receive review requests, the CODEOWNERS file must be on the b
 
 CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.
 
-To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. 
+To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry.
 {% endif %}
 
 ## CODEOWNERS syntax
@@ -103,11 +103,11 @@ apps/ @octocat
 # will require approval from @doctocat or @octocat.
 /scripts/ @doctocat @octocat
 
-# In this example, @octocat owns any file in the `/apps` 
-# directory in the root of your repository except for the `/apps/github` 
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
 # subdirectory, as its owners are left empty.
 /apps/ @octocat
-/apps/github 
+/apps/github
 ```
 ### Syntax exceptions
 There are some syntax rules for gitignore files that do not work in CODEOWNERS files:
@@ -116,7 +116,7 @@ There are some syntax rules for gitignore files that do not work in CODEOWNERS f
 - Using `[ ]` to define a character range
 
 ## CODEOWNERS and branch protection
-Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." 
+Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
 
 
 ## Further reading
diff --git a/data/reusables/github-actions/docker-container-os-support.md b/data/reusables/github-actions/docker-container-os-support.md
index 8dc5f40b5c..e334bce18c 100644
--- a/data/reusables/github-actions/docker-container-os-support.md
+++ b/data/reusables/github-actions/docker-container-os-support.md
@@ -1,6 +1,6 @@
 {% note %}
 
-**Note:** If your workflows use Docker container actions or service containers, then you must use a Linux runner:
+**Note:** If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runner:
 
 * If you are using {% data variables.product.prodname_dotcom %}-hosted runners, you must use an Ubuntu runner.
 * If you are using self-hosted runners, you must use a Linux machine as your runner and Docker must be installed.
diff --git a/lib/enterprise-dates.json b/lib/enterprise-dates.json
index 605d83cb3d..fd5411945d 100644
--- a/lib/enterprise-dates.json
+++ b/lib/enterprise-dates.json
@@ -118,5 +118,13 @@
   "3.6": {
     "releaseDate": "2022-07-19",
     "deprecationDate": "2023-08-16"
+  },
+  "3.7": {
+    "releaseDate": "2022-10-04",
+    "deprecationDate": "2023-11-08"
+  },
+  "3.8": {
+    "releaseDate": "2023-02-07",
+    "deprecationDate": "2024-03-07"
   }
 }
\ No newline at end of file
diff --git a/lib/excluded-links.js b/lib/excluded-links.js
index 3452045cac..44ed1073e7 100644
--- a/lib/excluded-links.js
+++ b/lib/excluded-links.js
@@ -31,5 +31,4 @@ export default [
   'https://www.vmware.com/products/esxi-and-esx.html',
   'https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5',
   'https://wiki.oasis-open.org/security',
-  'https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/',
 ]
diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json
index 76b56df4fd..3cfcfdb339 100644
--- a/lib/rest/static/decorated/api.github.com.json
+++ b/lib/rest/static/decorated/api.github.com.json
@@ -34221,86 +34221,6 @@
       }
     ]
   },
-  {
-    "verb": "delete",
-    "requestPath": "/reactions/{reaction_id}",
-    "serverUrl": "https://api.github.com",
-    "parameters": [
-      {
-        "name": "reaction_id",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "integer"
-        },
-        "descriptionHTML": ""
-      }
-    ],
-    "x-codeSamples": [
-      {
-        "lang": "Shell",
-        "source": "curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/reactions/42",
-        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/reactions/42</code></pre>"
-      },
-      {
-        "lang": "JavaScript",
-        "source": "await octokit.request('DELETE /reactions/{reaction_id}', {\n  reaction_id: 42\n})",
-        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'DELETE /reactions/{reaction_id}'</span>, {\n  <span class=\"hljs-attr\">reaction_id</span>: <span class=\"hljs-number\">42</span>\n})\n</code></pre>"
-      }
-    ],
-    "summary": "Delete a reaction (Legacy)",
-    "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/rest/reference/teams#discussion-comments).",
-    "tags": [
-      "reactions"
-    ],
-    "operationId": "reactions/delete-legacy",
-    "externalDocs": {
-      "description": "API method documentation",
-      "url": "https://docs.github.com/rest/reference/reactions/#delete-a-reaction-legacy"
-    },
-    "x-github": {
-      "githubCloudOnly": false,
-      "enabledForGitHubApps": true,
-      "removalDate": "2021-02-21",
-      "deprecationDate": "2020-02-26",
-      "category": "reactions",
-      "subcategory": null
-    },
-    "deprecated": true,
-    "slug": "delete-a-reaction-legacy",
-    "category": "reactions",
-    "categoryLabel": "Reactions",
-    "notes": [],
-    "bodyParameters": [],
-    "descriptionHTML": "<p><strong>Deprecation Notice:</strong> This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this <a href=\"https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/\">blog post</a>.</p>\n<p>OAuth access tokens require the <code>write:discussion</code> <a href=\"https://docs.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/\">scope</a>, when deleting a <a href=\"https://docs.github.com/rest/reference/teams#discussions\">team discussion</a> or <a href=\"https://docs.github.com/rest/reference/teams#discussion-comments\">team discussion comment</a>.</p>",
-    "responses": [
-      {
-        "httpStatusCode": "204",
-        "httpStatusMessage": "No Content",
-        "description": "<p>Response</p>"
-      },
-      {
-        "httpStatusCode": "304",
-        "httpStatusMessage": "Not Modified",
-        "description": "<p>Not modified</p>"
-      },
-      {
-        "httpStatusCode": "401",
-        "httpStatusMessage": "Unauthorized",
-        "description": "<p>Requires authentication</p>"
-      },
-      {
-        "httpStatusCode": "403",
-        "httpStatusMessage": "Forbidden",
-        "description": "<p>Forbidden</p>"
-      },
-      {
-        "httpStatusCode": "410",
-        "httpStatusMessage": "Gone",
-        "description": "<p>Gone</p>"
-      }
-    ]
-  },
   {
     "verb": "get",
     "requestPath": "/repos/{owner}/{repo}",
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index a2ffaff8ed..99d15bcf4c 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -24966,86 +24966,6 @@
       }
     ]
   },
-  {
-    "verb": "delete",
-    "requestPath": "/reactions/{reaction_id}",
-    "serverUrl": "https://{hostname}/api/v3",
-    "parameters": [
-      {
-        "name": "reaction_id",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "integer"
-        },
-        "descriptionHTML": ""
-      }
-    ],
-    "x-codeSamples": [
-      {
-        "lang": "Shell",
-        "source": "curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/reactions/42",
-        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/reactions/42</code></pre>"
-      },
-      {
-        "lang": "JavaScript",
-        "source": "await octokit.request('DELETE /reactions/{reaction_id}', {\n  reaction_id: 42\n})",
-        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'DELETE /reactions/{reaction_id}'</span>, {\n  <span class=\"hljs-attr\">reaction_id</span>: <span class=\"hljs-number\">42</span>\n})\n</code></pre>"
-      }
-    ],
-    "summary": "Delete a reaction (Legacy)",
-    "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/github-ae@latest/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/github-ae@latest/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/github-ae@latest/rest/reference/teams#discussion-comments).",
-    "tags": [
-      "reactions"
-    ],
-    "operationId": "reactions/delete-legacy",
-    "externalDocs": {
-      "description": "API method documentation",
-      "url": "https://docs.github.com/github-ae@latest/rest/reference/reactions/#delete-a-reaction-legacy"
-    },
-    "x-github": {
-      "githubCloudOnly": false,
-      "enabledForGitHubApps": true,
-      "removalDate": "2021-02-21",
-      "deprecationDate": "2020-02-26",
-      "category": "reactions",
-      "subcategory": null
-    },
-    "deprecated": true,
-    "slug": "delete-a-reaction-legacy",
-    "category": "reactions",
-    "categoryLabel": "Reactions",
-    "notes": [],
-    "bodyParameters": [],
-    "descriptionHTML": "<p><strong>Deprecation Notice:</strong> This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this <a href=\"https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/\">blog post</a>.</p>\n<p>OAuth access tokens require the <code>write:discussion</code> <a href=\"https://docs.github.com/github-ae@latest/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/\">scope</a>, when deleting a <a href=\"https://docs.github.com/github-ae@latest/rest/reference/teams#discussions\">team discussion</a> or <a href=\"https://docs.github.com/github-ae@latest/rest/reference/teams#discussion-comments\">team discussion comment</a>.</p>",
-    "responses": [
-      {
-        "httpStatusCode": "204",
-        "httpStatusMessage": "No Content",
-        "description": "<p>Response</p>"
-      },
-      {
-        "httpStatusCode": "304",
-        "httpStatusMessage": "Not Modified",
-        "description": "<p>Not modified</p>"
-      },
-      {
-        "httpStatusCode": "401",
-        "httpStatusMessage": "Unauthorized",
-        "description": "<p>Requires authentication</p>"
-      },
-      {
-        "httpStatusCode": "403",
-        "httpStatusMessage": "Forbidden",
-        "description": "<p>Forbidden</p>"
-      },
-      {
-        "httpStatusCode": "410",
-        "httpStatusMessage": "Gone",
-        "description": "<p>Gone</p>"
-      }
-    ]
-  },
   {
     "verb": "get",
     "requestPath": "/repos/{owner}/{repo}",
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index d3eee146e8..16f9f63854 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -125023,125 +125023,6 @@
         }
       }
     },
-    "/reactions/{reaction_id}": {
-      "delete": {
-        "summary": "Delete a reaction (Legacy)",
-        "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/rest/reference/teams#discussion-comments).",
-        "tags": [
-          "reactions"
-        ],
-        "operationId": "reactions/delete-legacy",
-        "externalDocs": {
-          "description": "API method documentation",
-          "url": "https://docs.github.com/rest/reference/reactions/#delete-a-reaction-legacy"
-        },
-        "parameters": [
-          {
-            "name": "reaction_id",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "integer"
-            }
-          }
-        ],
-        "responses": {
-          "204": {
-            "description": "Response"
-          },
-          "304": {
-            "description": "Not modified"
-          },
-          "403": {
-            "description": "Forbidden",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          },
-          "401": {
-            "description": "Requires authentication",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          },
-          "410": {
-            "description": "Gone",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        "x-github": {
-          "githubCloudOnly": false,
-          "enabledForGitHubApps": true,
-          "removalDate": "2021-02-21",
-          "deprecationDate": "2020-02-26",
-          "category": "reactions",
-          "subcategory": null
-        },
-        "deprecated": true
-      }
-    },
     "/repos/{owner}/{repo}": {
       "get": {
         "summary": "Get a repository",
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index 2dbc75a754..05a7106f3c 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -77292,125 +77292,6 @@
         }
       }
     },
-    "/reactions/{reaction_id}": {
-      "delete": {
-        "summary": "Delete a reaction (Legacy)",
-        "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/github-ae@latest/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/github-ae@latest/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/github-ae@latest/rest/reference/teams#discussion-comments).",
-        "tags": [
-          "reactions"
-        ],
-        "operationId": "reactions/delete-legacy",
-        "externalDocs": {
-          "description": "API method documentation",
-          "url": "https://docs.github.com/github-ae@latest/rest/reference/reactions/#delete-a-reaction-legacy"
-        },
-        "parameters": [
-          {
-            "name": "reaction_id",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "integer"
-            }
-          }
-        ],
-        "responses": {
-          "204": {
-            "description": "Response"
-          },
-          "304": {
-            "description": "Not modified"
-          },
-          "403": {
-            "description": "Forbidden",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          },
-          "401": {
-            "description": "Requires authentication",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          },
-          "410": {
-            "description": "Gone",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        "x-github": {
-          "githubCloudOnly": false,
-          "enabledForGitHubApps": true,
-          "removalDate": "2021-02-21",
-          "deprecationDate": "2020-02-26",
-          "category": "reactions",
-          "subcategory": null
-        },
-        "deprecated": true
-      }
-    },
     "/repos/{owner}/{repo}": {
       "get": {
         "summary": "Get a repository",
diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br
index 2f9c75a350..c518b4e031 100644
--- a/lib/search/indexes/github-docs-3.0-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:47f2a1bb71c44eb3c14690449ffc37eafb1684500109ff16eb534a993a1ab4e2
-size 660732
+oid sha256:ad495955bf4dbf471ff73384117657af07d4febfd430d332410e6487a4601867
+size 661523
diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br
index e68bd8a880..8a8fb0ec81 100644
--- a/lib/search/indexes/github-docs-3.0-cn.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4a9da08bd9e586ce171f93454eac32c2885c741e7ac774ed397e0ea3fb0c9308
-size 1377623
+oid sha256:5ad03c624fd895682493a613f0d52d592cc28f45f0157394c24c6bcb34d49b57
+size 1377641
diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br
index c2c45e9135..c1e3abba5b 100644
--- a/lib/search/indexes/github-docs-3.0-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c8b98f298f8c276301a1eb4f0d599b794d8dc950ec13c229ed53d431b387374c
-size 980831
+oid sha256:55092e613eab6c38284ddc5f695466d16fe67f28eb662881ce138a09c3bdab5b
+size 979739
diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br
index adb1ffa749..aee27bc45a 100644
--- a/lib/search/indexes/github-docs-3.0-en.json.br
+++ b/lib/search/indexes/github-docs-3.0-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b1ca84b937c9dd0aa0eb580638c887f7af43135dde7700fe9a797a79eeaacbb5
-size 3989912
+oid sha256:e46fc8b08c5dafa39171231434e113181e481e70bc936c26f4af77be35192a34
+size 3989151
diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br
index a776c78ca4..0db060ba07 100644
--- a/lib/search/indexes/github-docs-3.0-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:32978fe3141fee7148015cc9051fe4f9c550faaf1b4bc42c8bc181c2bf7ebe2d
-size 614498
+oid sha256:d9a44cad36399623e67812bd04fadd4b301506dba1f704e66746f918dae9aa29
+size 614734
diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br
index 58439eefad..4ad4f138da 100644
--- a/lib/search/indexes/github-docs-3.0-es.json.br
+++ b/lib/search/indexes/github-docs-3.0-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a1b13e1411ad4db2b7592dd952ab4702c7be942635045b9ce09fab80108e06b7
-size 2572359
+oid sha256:666bb6ea14b3285420cb53ddfd61b96e8c54bfdee5586e557909d52306081db8
+size 2571661
diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br
index 4800d5cae8..a2080720ba 100644
--- a/lib/search/indexes/github-docs-3.0-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2e41390628d2a6af9fa323fcc78b96b1fa867f2337a8a1d68a9a414916cfa0a8
-size 680711
+oid sha256:8a5f856f1cd6f32b5ccc30c7c9700e78391d0620dbc71ed6b219fef207d25e7d
+size 680096
diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br
index 3b950b0912..12ea331452 100644
--- a/lib/search/indexes/github-docs-3.0-ja.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4056ffa70370838f88b9fe2694e257c4692bcd29a0a6693a0fe969b5d03d68d4
-size 3602301
+oid sha256:28717e93df6608c3ce5d73722a0fe28096888320057932f266fead61e0c56e8a
+size 3598394
diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br
index 5b725e221f..b883f52843 100644
--- a/lib/search/indexes/github-docs-3.0-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1318284320faf8b349cc340d983cab28fc11ef18e0698d81c5fa2fa93566a4c6
-size 605075
+oid sha256:bc5c4b1ac7bd72100f98078b8f1d69e776471a24e9bc0514141eb3e98c8b3023
+size 606078
diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br
index c75e11788e..c2b37c3332 100644
--- a/lib/search/indexes/github-docs-3.0-pt.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5f95b862e592737ec7372226f74f6e88576a6819715de17641238337fcc6a990
-size 2468070
+oid sha256:f1f741dd3dcda753c9307bd336f0c4a00ca300375155d51e7d0db51e0918bd25
+size 2466806
diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br
index 54acb07ef7..a0c35d659c 100644
--- a/lib/search/indexes/github-docs-3.1-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:eddf78f62bffcadb7942c66be544a78c076e5cabc04c4e208f84e9f22ce8224b
-size 675183
+oid sha256:2401c7797a3c30fba923d0ed54331df67911e2d85292628a3327e288d6e3d3b2
+size 675282
diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br
index d7b35dfbf1..ae55475060 100644
--- a/lib/search/indexes/github-docs-3.1-cn.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4d84604ee31476e632a44a9424a1b1f5beb7db2cdae9d4550ae11b84e5251d38
-size 1413778
+oid sha256:95c2321b8587ad217d4c2558498615bcbe186fcff1de15d950ca484f037060d8
+size 1413900
diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br
index 7da0340f6f..1322ac2d7b 100644
--- a/lib/search/indexes/github-docs-3.1-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:488e795fdf2c77ec061c6ec97623e297e3c657a02321538a9ec59d1f3ca98f69
-size 1006261
+oid sha256:f0c6b6f75fc051cefc0f5a1c5307c8c3d4e0d8d20c87f65dc39977997b389560
+size 1005018
diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br
index fcc1aa688a..fd82045ead 100644
--- a/lib/search/indexes/github-docs-3.1-en.json.br
+++ b/lib/search/indexes/github-docs-3.1-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:923e43b3a50c22d686834c514dd02c381ded234cdc53f5deefec92806fb2e285
-size 4079033
+oid sha256:b8d854bb453c129c459229683f1f386273f8ac642e371b85aa8716f542974cb9
+size 4077692
diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br
index cb2f0d2f98..1fabbd787c 100644
--- a/lib/search/indexes/github-docs-3.1-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0011455a5d11bc33ba2af5c5703da6698ae6b9d746a89ae88a68c4cca1664185
-size 627075
+oid sha256:f590dc84c133e2e733cadde4788fd36bbd4992495a44c05e8e9641d4f0c04315
+size 626202
diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br
index cd2aee087b..33561b5e9b 100644
--- a/lib/search/indexes/github-docs-3.1-es.json.br
+++ b/lib/search/indexes/github-docs-3.1-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f6b547cf671384d5e632f5c75a289a462b4b4db8d8c417ce2469bf88a3bcd503
-size 2632887
+oid sha256:47ac7e471aed6604b9edcce596f17501cb2741bf4182e7c42c84503a25d83d7b
+size 2632609
diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br
index 2e5a952e8c..5ac5cc2cce 100644
--- a/lib/search/indexes/github-docs-3.1-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:30794b66196dca5d7cd844e7a1ec9c7ff64fec8d566db0860fdda0c4db2ac500
-size 694092
+oid sha256:a6726d64418ea8c768e9a5e72f0f377e49b48a2f4ed8e2905a8d6eef016677cf
+size 694174
diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br
index 41f57e86a4..30e91828ac 100644
--- a/lib/search/indexes/github-docs-3.1-ja.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bafc02f6e8e424b0cf7be57da2083b8e91f809698e3d44e835d5c80d662fa88c
-size 3680366
+oid sha256:7033475bd2828f6236c887b3746d8a93ec52d550c56422e646ae55063d632c94
+size 3679134
diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br
index c6e3272dc8..a5c326dc79 100644
--- a/lib/search/indexes/github-docs-3.1-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:92d1fa4bd98655c1957297d7206be6953527255bae9740c851fea9412144958e
-size 617448
+oid sha256:188b07f5c8c04bccd252676415a3ced2cb4b968f4f578056b70dbc6b4865ad33
+size 617214
diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br
index 2e58628d72..ce0564cadb 100644
--- a/lib/search/indexes/github-docs-3.1-pt.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d767f63307ac25a99e08d07ef484fe69c7e3805ebe9959d67f636847cb6876fc
-size 2519795
+oid sha256:fd658c5fb357920bd1f49349f79097d59f130670e913ed009e0885b0dc34b861
+size 2519431
diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br
index b16bfe13be..5496bfa391 100644
--- a/lib/search/indexes/github-docs-3.2-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:34829eb8612d1f810af323f5581eb62e33cd0763ca0787d76847bd923674c818
-size 691980
+oid sha256:915a06d90236340a4b4372b93e44a55434acd531eca3ded771defbd13e4aba4b
+size 690251
diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br
index 278efdccba..4062f76132 100644
--- a/lib/search/indexes/github-docs-3.2-cn.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1e9af186991894f3b9dfaadb97e5ae577944ce8bf918c4a342e1f5b5e57154a7
-size 1446142
+oid sha256:233423a48886ea0fb7bd542f40cc7f45b2e41eb9f730882e9e1a428ac9e0e55a
+size 1446159
diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br
index d7cdf912ce..f04eec3086 100644
--- a/lib/search/indexes/github-docs-3.2-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bf7e6e4e93c01d6345b1a08da2750b2253fda1ba9c0510aa6238edd2ed708d38
-size 1039550
+oid sha256:869eacd89cb812dfb884e06ce77f5335a2aa73069cc38a2f776363cf168eb9da
+size 1037730
diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br
index ad9fa71d20..ca507634f5 100644
--- a/lib/search/indexes/github-docs-3.2-en.json.br
+++ b/lib/search/indexes/github-docs-3.2-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3223e5113f0e3b18e10aa0a9b350609495aa608291e285a3457c1d0f37db0e8d
-size 4214510
+oid sha256:df7de3478533adc4e4e6f7586d7ac25acac20cd642f7abd92d2525addc1909d6
+size 4210326
diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br
index dbd86d63c3..076ed34b5a 100644
--- a/lib/search/indexes/github-docs-3.2-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d2701762992d04ae5a4256235dc5a8322028ca01071f9b947253ee5e66dc6676
-size 641530
+oid sha256:c417de5bc9d32897568c66608db3fab9a532fb626f2272c58a95ec1c647ef669
+size 640659
diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br
index b38aeec215..7f9b2061a7 100644
--- a/lib/search/indexes/github-docs-3.2-es.json.br
+++ b/lib/search/indexes/github-docs-3.2-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e24e0061ac20fb620e949c00c7fdbbc063236400cc8e7074ff1a5160873eea5e
-size 2696420
+oid sha256:6f447a6f7f487b5beb870e10a4744753a2acef614a0c6fba62ad1e55894af2b0
+size 2692986
diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br
index c0f8bc855c..322cab6175 100644
--- a/lib/search/indexes/github-docs-3.2-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:78b5354fd197efc35df0c812472479e001e29d8e307fccb5a54c7f734c3d7632
-size 708963
+oid sha256:b4479845ed1bdc56a665303b5e228dfbbe19e048c883b240d177eebccafd564f
+size 707720
diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br
index 4e4912cfe0..e1482d598e 100644
--- a/lib/search/indexes/github-docs-3.2-ja.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ca0907e1983c6cad844d4f51413a8e836900f3c5535e082cfce9b251e782b974
-size 3765008
+oid sha256:805de48302d421d89cb7de5ed87f563b7c28e6bc31856d884073221228911db5
+size 3760558
diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br
index 681c997769..b448a4302d 100644
--- a/lib/search/indexes/github-docs-3.2-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:beab35c298cf0ceaaae95fcf8a0366c0610f58368f79851ff835c7d1dd9279d6
-size 632967
+oid sha256:bdf9412b1ee1727d2ef8ec8a8dae728eebe5a64509f1e4198ea1ae046de3bf2b
+size 630968
diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br
index 9c042fce4c..311c83b542 100644
--- a/lib/search/indexes/github-docs-3.2-pt.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1fe6ecafeb217e7ce74fe7cf2a38b15e263f04a0ba823cbae20f4caeb116edea
-size 2580079
+oid sha256:950db6f7dcd9d2ee5d0ac691126c7066e8640f0e00cdaa0e38acd654257cccb2
+size 2578754
diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br
index 5062a07caf..e436e5679e 100644
--- a/lib/search/indexes/github-docs-3.3-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3bbf2f35668d8050bf520aca714d861fbc22fd4a102895280b395985466deaa4
-size 712820
+oid sha256:0a72f5dd062b0e1628016f706906342a3e198f248bfb0951ed0c4ba8472c5330
+size 712899
diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br
index 82d132e442..aff5c785ae 100644
--- a/lib/search/indexes/github-docs-3.3-cn.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0cef26bbf55015e1be4e51a5ac11530b9611633cbf6985e3e2562f2ba605f0b0
-size 1505929
+oid sha256:b4e6db2740dbb871cfbcdc730b845d1276a0af00a22e66eaa30839dc2706933b
+size 1505664
diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br
index dc06f04ae0..f90f85a08a 100644
--- a/lib/search/indexes/github-docs-3.3-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1e124cd6fcaa95e2df0edd42426c82d395b9f74a69e49ab4d64db9d70b9d9235
-size 1079134
+oid sha256:96e6d0ac4483be6d5a2b0567f17a1ddb414058703c7607e080fb23fe045e7d64
+size 1073502
diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br
index a8873c67da..9e1d777482 100644
--- a/lib/search/indexes/github-docs-3.3-en.json.br
+++ b/lib/search/indexes/github-docs-3.3-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c98b85d478d58207e212583715b6e6c1b4048c27316f5c6af1a3eca6dad52198
-size 4315518
+oid sha256:06d26640d0668fce291b6b99c92b0a43ab7f2fc36843112423923a0d52e864ab
+size 4313205
diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br
index fc6babe2a7..0123244854 100644
--- a/lib/search/indexes/github-docs-3.3-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bd30526d5517c1c32711708f15073af206a954fd870b21fb1bb5ae672331beba
-size 661016
+oid sha256:ed3ef73ec189760efa247b361d00d011925d70b25aa3f67754ef9d52ca735cd6
+size 660641
diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br
index 576f25f1e9..c0a71c641b 100644
--- a/lib/search/indexes/github-docs-3.3-es.json.br
+++ b/lib/search/indexes/github-docs-3.3-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:de49151c9f250aa5aa6ae7aa10eb82a86c49a5c3f60e7450658cee4bec699b25
-size 2797541
+oid sha256:832bd101501946de847558f5048bf61f9b3286f6079e8f9445101b3bbf41e6d6
+size 2795859
diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br
index b4c54efb02..e8ccd829b7 100644
--- a/lib/search/indexes/github-docs-3.3-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:13330f28c9e496df248bd006e3b0bb3d825bf1578b62c604e70e2e3ee00da218
-size 732092
+oid sha256:0aa05ef0f2c91bda47f3b13a415191efa2053ef0d478ce5f0363e1c547d34a28
+size 730845
diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br
index ca6a870124..e02835669b 100644
--- a/lib/search/indexes/github-docs-3.3-ja.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f9f5e19dd7f1c7780e4f9aab9647cb98de82c4d7d958556b665f0ff73084cbf4
-size 3891349
+oid sha256:c6b3477463aa7ce1aa714f23cfb62a755c3c6000cfd16ca26461808ffd3300b0
+size 3885440
diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br
index ce6b769928..821d5d256a 100644
--- a/lib/search/indexes/github-docs-3.3-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f56744f881b0257b612aeec6fe657870327d53ce5d69e9582a9c863f3bdb9b8a
-size 650798
+oid sha256:64124d66a630fec0d14d2078d44c12b6a0e805a86404a92bf9efeea16d0b4a2a
+size 650744
diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br
index 38b406f19e..9fd17d9c9d 100644
--- a/lib/search/indexes/github-docs-3.3-pt.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:11cc0508cc1ad069ffe751d3e0ae676ae949aeaa0e57fd2b5ba002a6a2ba5ce5
-size 2661406
+oid sha256:d8d6e54b1b2efde0044ec8e5a13ae4f9e15b13b8c0162119de864be22330eb33
+size 2659878
diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
index 7c7f76190f..5f81ac7a4a 100644
--- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:751deeb265410a437d6aaea7b61d1ef8f8ea761e08231c13ad6608add4d610c2
-size 914158
+oid sha256:b6b70df7657927142c3044994d780da0232e81bf5c81d92f29228be2d286cda9
+size 913561
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index bf887e0ba5..86c034d408 100644
--- a/lib/search/indexes/github-docs-dotcom-cn.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2774a524a7d307eb599fec438272dcbba4620ed18fc419103efa4df8388146e5
-size 1681024
+oid sha256:d22d36852b06fa338883bc71f72e2865fbb38a3be87b4e6894c1355737935f79
+size 1683070
diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br
index be66c28cca..c62d147b88 100644
--- a/lib/search/indexes/github-docs-dotcom-en-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:76a3fabbb2c816e60d0f1856ae8a4f7b63aa657790209871367af7ebd33995b1
-size 1366262
+oid sha256:5b2df0016b9d815939adb5fad570038317bd55ee5feed797c20a71386bd8de4f
+size 1362871
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 283ea2d37a..b250da674e 100644
--- a/lib/search/indexes/github-docs-dotcom-en.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:831f2c630befa95f7b0dc1195244bede9c1242a8d240ae033ad4c475dabc88b6
-size 5205576
+oid sha256:096b3892b67ffd9137c3eb7b230e30e1386d53aa267da609136cb1fc20f0cb96
+size 5202022
diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br
index 90b88fd5b1..ac22af40b1 100644
--- a/lib/search/indexes/github-docs-dotcom-es-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8c256c303a2065ef015f03b4726cef00d7516f948f38896b5acdfea23664867a
-size 830646
+oid sha256:7b5609f12f94015845b5c548081c549a2c98fc248271c5a5338bea5a1ce563c2
+size 829425
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 86599dbde1..5eee17384f 100644
--- a/lib/search/indexes/github-docs-dotcom-es.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:820e67288c8ede26cafa5481db87db665d8c2c0d505985a75d62d4455ad671fb
-size 3348903
+oid sha256:b34a6c0bc4b9c4a46e1ef559a760ae13674435787aef9eed54bc893ed8aca0f2
+size 3352707
diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
index a364c04ce6..93a043d601 100644
--- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5d789fb3a6eeda67b45e715cfa15764e605fc0a2c1fd0e211b7c2d82446fa4c9
-size 933494
+oid sha256:3d33f9a7393939783e4d3e3096e6ca5503870b34433938f08a03fd0542a34292
+size 932489
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index 1405858fa6..5f6370c895 100644
--- a/lib/search/indexes/github-docs-dotcom-ja.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e20f510633d1a7c158b6d7bf53c80538713d92f66aa79310c17e1b412a5a9426
-size 4751551
+oid sha256:3ab3c7ddb0245fc369a36ea67ce0042c532fc022b2f2a5b4726ee4d2218e60e4
+size 4746133
diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
index b214b91fac..cc531ca372 100644
--- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:eb79a4c7712539d04ffcf6723f5a72c348aad81b363a8993a6b95552d788d87c
-size 820063
+oid sha256:ba48313cf5878d45ce342758356c028dde6c019d767998d7df71906730385c46
+size 820358
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index 4f8ad22cf5..485ea766d5 100644
--- a/lib/search/indexes/github-docs-dotcom-pt.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:da8a5dc9ac23bc19b0ba2201c8b19bc252a7d92a4db02a0d9fb708f62aba2afd
-size 3199105
+oid sha256:4be930827ff2cab6ad6c18da618498d8da5445e4abd0c73e56ee6dc6deac9ec4
+size 3195820
diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br
index 59cb8c3a0c..22b012d113 100644
--- a/lib/search/indexes/github-docs-ghae-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:523c008ead84776d546b2295dc26933ded47bcc1be4bbd1d4ae28f77f580550a
-size 559246
+oid sha256:96a76ad2ae2e23d2cafc71fbe5a760e6e7ede83bef7635cc03ba4906c9eb1f1e
+size 559467
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index dfbeee4974..adb11dd98e 100644
--- a/lib/search/indexes/github-docs-ghae-cn.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e9706d9c59162558b254fc5813830ac8ca11ed4611c6cc19af1e360612daf1f8
-size 1127281
+oid sha256:3754c6bda2308aedba5d66acc6ea156f8f64969b462a733146c26d8d3e93b8de
+size 1127318
diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br
index 6a1baba942..1b978a9a6b 100644
--- a/lib/search/indexes/github-docs-ghae-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dbd9c5ab249a73d044d984f08977aeadfcaf6c001fa598f7d29e27158c98db68
-size 857900
+oid sha256:728017aa0e305bca0e37bef4f85e8e42fb7e4a2e8e08814713a665945aa72c49
+size 858190
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index 682a72ae01..1746bfa934 100644
--- a/lib/search/indexes/github-docs-ghae-en.json.br
+++ b/lib/search/indexes/github-docs-ghae-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be65f4807bdd555bd89024d1077a6e7e7de6c56af3f49c00ede7b26b9998a751
-size 3436123
+oid sha256:d1227d56b3eb198f83640056bd743b4f234f1b2ad20644ea03f06eff34529284
+size 3434582
diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br
index 9d6cbb3a32..9932f4e43c 100644
--- a/lib/search/indexes/github-docs-ghae-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:10bbd20fd9ffea263a4a6a0a5ae846c0981743c0eaa301d6984c6689039f61f4
-size 520267
+oid sha256:c4fd97bb4345d12f0e063e70b4b376f1d53b63f1aabf95387e7ec355b601da61
+size 519495
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index 57d4a4655f..5b5ab73469 100644
--- a/lib/search/indexes/github-docs-ghae-es.json.br
+++ b/lib/search/indexes/github-docs-ghae-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a7333febe7ffe6bcb0176ddad6a57dab5d1c36017e0f0934f614a2c32f7e1fd8
-size 2117042
+oid sha256:811e8f249e5c028e8a09fda609c702d42940de21060152bd8e65f7abc6d5480d
+size 2115662
diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br
index ee41bccd07..268ef9fec8 100644
--- a/lib/search/indexes/github-docs-ghae-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:adad47de10961bcfe088d7192c6d29f7719bc95a6b1fb109d1de99080f43a807
-size 572337
+oid sha256:ad63cf60d4399157b2aa910d81520aeacde42dc5552aa4199bf82f067434a0a6
+size 571996
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 64c7521529..c80a7aa3eb 100644
--- a/lib/search/indexes/github-docs-ghae-ja.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:af9b793135c26c3bef76a83fe5675817354ecec19ddb0cc61ebb1d54eebbe47f
-size 2933511
+oid sha256:7764209b0698957bd0975e15b3436412dcc820545a621cf5114c0c3ba50b9980
+size 2931596
diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br
index 99701f6313..96cf29437e 100644
--- a/lib/search/indexes/github-docs-ghae-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:04a911707894a670345c525a13e99285f954e969f7d24ec72be4177f7ca9c9b1
-size 513120
+oid sha256:14d93c2b5c45c957317bcef3cba11171fe8a6e06e694876a6a124d183727b26a
+size 512144
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index a2c06e9751..00facb7114 100644
--- a/lib/search/indexes/github-docs-ghae-pt.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f01d21d21ecabfb4a22bb46d77d04c4ede421de43dc97133daad3586f8b5d202
-size 2011354
+oid sha256:3f8f63042d5f74253c9a021b4aede4f7248338f5a7724744223393597d496049
+size 2007530
diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br
index 5f88e897e6..d6c3c4e260 100644
--- a/lib/search/indexes/github-docs-ghec-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2d158e4655e7dc176ccfdbb332127244e5db2e4714109786527a9b4899a2aeb5
-size 841139
+oid sha256:ab59b269a618453c2587d881603ba915aca0f88a97e5bce2bd4ef2aa19d61575
+size 841049
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index 8d00b71695..e6ae96aa17 100644
--- a/lib/search/indexes/github-docs-ghec-cn.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4a12223ff160d45727ca3e8e34f0037d4eee674e2aed5ddd38b86daf47f510a7
-size 1750468
+oid sha256:607042ae1f0da3ea6feb304b9a84de2f05722c130c875c107a62ad12050fbb0a
+size 1751854
diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br
index 7a68c9f415..0ee5a31d5b 100644
--- a/lib/search/indexes/github-docs-ghec-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8c18c7caaa4ee265bdab64886f3bcf5ee8dd7cf8035b8412a27a82e05dca82ec
-size 1240503
+oid sha256:4527da07c61aa62b2cbf4592e9c8b5f66267a1a7620097973530bc333428ce90
+size 1239184
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index 2d63282116..4237a4a7ac 100644
--- a/lib/search/indexes/github-docs-ghec-en.json.br
+++ b/lib/search/indexes/github-docs-ghec-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e45f77dcc6138aba633fb7ac1d8cf78b8673e3b0f86bff1eacba2a4d07548b03
-size 4986557
+oid sha256:adae1cf914eeef685804ab4aabf56989b13a1c08ec29b673424254df40c45005
+size 4983993
diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br
index 5b1f9d71b7..00d5b80761 100644
--- a/lib/search/indexes/github-docs-ghec-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6b44f7963559dcaaea15d840de2ba347f4c0c7f6b55df6097b70d20b0769d7d4
-size 788407
+oid sha256:ff4d540983d43a8b4d7efccfcd9f6d6fd57488819fb46aa7c7cf781ebc2a908f
+size 788733
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 47eb5dd0b1..28d781eb01 100644
--- a/lib/search/indexes/github-docs-ghec-es.json.br
+++ b/lib/search/indexes/github-docs-ghec-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7aa2764125d915c8a7456dba422f7d948e6dcdc6995609b6f629d860d9811f9d
-size 3338450
+oid sha256:8dbb00d9602ee4fee16709a27ed16e6927beac56ff57f9d7c385f78b0abe8b88
+size 3339849
diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br
index 987567dc32..78acc66122 100644
--- a/lib/search/indexes/github-docs-ghec-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b7d793bd277c6ef95acff91b5ed05b545f78378c01b34ec3b33ace9e8f10dc2f
-size 863368
+oid sha256:4930f50255ca5f8bc21b734350e0d5680fc9806513b329c9be547b7993d7a097
+size 861784
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index 92174892ff..5703332151 100644
--- a/lib/search/indexes/github-docs-ghec-ja.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9407d83306f92fdeedfe304a7eb6faab2166dcb854e760002108ae4c14591b55
-size 4619826
+oid sha256:4f0e05861b6045d32c923a45dc4dc89336fe6399222ee7729c71b6354d021c5d
+size 4613765
diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br
index 9cc63553e5..6510cc3cea 100644
--- a/lib/search/indexes/github-docs-ghec-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f97d40dd41595c76a7de608873e70795dab88038dd784973c08b243322e98de0
-size 778310
+oid sha256:4efb5e828997ef06f7901b3bedbb848fd1de6fce81e7afac22f380d69f58bdcd
+size 777032
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index cb476eeefc..01e345a4f2 100644
--- a/lib/search/indexes/github-docs-ghec-pt.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:40f8fdfc6fe07fb00a40e3268c43db774ff7fca8edc4b1c4d3bf0a9602502010
-size 3178281
+oid sha256:2223b6ab597be5bb310880ecbda27ed000ed67d1a1ffce8ba89725ff1f152b97
+size 3174248
diff --git a/middleware/archived-enterprise-versions-assets.js b/middleware/archived-enterprise-versions-assets.js
index 540aab8d5d..2b36d17c5e 100644
--- a/middleware/archived-enterprise-versions-assets.js
+++ b/middleware/archived-enterprise-versions-assets.js
@@ -15,12 +15,37 @@ const cacheControl = cacheControlFactory(60 * 60 * 24)
 // See also ./archived-enterprise-versions.js for non-CSS/JS paths
 
 export default async function archivedEnterpriseVersionsAssets(req, res, next) {
+  // Only match asset paths
+  // This can be true on /enterprise/2.22/_next/static/foo.css
+  // or /_next/static/foo.css
+  if (!patterns.assetPaths.test(req.path)) return next()
+
+  // We now know the URL is either /enterprise/2.22/_next/static/foo.css
+  // or the regular /_next/static/foo.css. But we're only going to
+  // bother looking it up on https://github.github.com/help-docs-archived-enterprise-versions
+  // if the URL has the enterprise bit in it, or if the path was
+  // /_next/static/foo.css *and* its Referrer had the enterprise
+  // bit in it.
+  if (
+    !(
+      patterns.getEnterpriseVersionNumber.test(req.path) ||
+      patterns.getEnterpriseServerNumber.test(req.path) ||
+      patterns.getEnterpriseVersionNumber.test(req.get('referrer')) ||
+      patterns.getEnterpriseServerNumber.test(req.get('referrer'))
+    )
+  ) {
+    return next()
+  }
+
+  // Now we know the URL is definitely not /_next/static/foo.css
+  // So it's probably /enterprise/2.22/_next/static/foo.css and we
+  // should see if we might find this in the proxied backend.
+  // But `isArchivedVersion()` will only return truthy if the
+  // Referrer header also indicates that the request for this static
+  // asset came from a page
   const { isArchived, requestedVersion } = isArchivedVersion(req)
   if (!isArchived) return next()
 
-  // Only match asset paths
-  if (!patterns.assetPaths.test(req.path)) return next()
-
   const assetPath = req.path.replace(`/enterprise/${requestedVersion}`, '')
   const proxyPath = path.join('/', requestedVersion, assetPath)
 
@@ -37,6 +62,28 @@ export default async function archivedEnterpriseVersionsAssets(req, res, next) {
     cacheControl(res)
     return res.send(r.body)
   } catch (err) {
-    return next(404)
+    // Primarly for the developers working on tests that mock
+    // requests. If you don't set up `nock` correctly, you might
+    // not realize that and think it failed for other reasons.
+    if (err.toString().includes('Nock: No match for request')) {
+      throw err
+    }
+
+    // It's important that we don't give up on this by returning a 404
+    // here. It's better to let this through in case the asset exists
+    // beyond the realm of archived enterprise versions.
+    // For example, image you load
+    // /enterprise-server@2.21/en/DOES/NOT/EXIST in your browser.
+    // Quickly, we discover that the proxying is failing because
+    // it didn't find a page called `/en/DOES/NOT/EXIST` over there.
+    // So, we proceed to render *our* 404 HTML page.
+    // Now, on that 404 page, it will reference static assets too.
+    // E.g. <link href="/_next/static/styles.css">
+    // These will thus be requested, with a Referrer header that
+    // forces us to give it a chance, but it'll find it can't find it
+    // but we mustn't return a 404 yet, because that
+    // /_next/static/styles.css will probably still succeed because the 404
+    // page is not that of the archived enterprise version.
+    return next()
   }
 }
diff --git a/middleware/handle-errors.js b/middleware/handle-errors.js
index 1ecffc2dd6..f27f60b43d 100644
--- a/middleware/handle-errors.js
+++ b/middleware/handle-errors.js
@@ -41,21 +41,9 @@ export default async function handleError(error, req, res, next) {
     // By default, Fastly will cache 404 responses unless otherwise
     // told not to.
     // See https://docs.fastly.com/en/guides/how-caching-and-cdns-work#http-status-codes-cached-by-default
-    // Most of the time, that's a good thing! Especially, if bombarded
-    // for some static asset that we don't have.
-    // E.g. `ab -n 10000 https://docs.github.com/assets/doesnotexist.png`
-    // But due to potential timing issue related to how the servers start,
-    // what might happen is that a new insteance comes up that
-    // contains `<script src="/_next/static/foo.1234.css">` in the HTML.
-    // The browser then proceeds to request /_next/static/foo.1234.css
-    // but this time it could be unluckily routed to a different instance
-    // that hasn't yet been upgraded, so they get a 404. And the CDN will
-    // notice this and cache it.
-    // Setting a tiny cache gets us a good compromise. It protects us
-    // against most stamping herds on 404s (thank you CDN!) but it also
-    // clears itself if you get that unlucky timing issue with rolling
-    // instances in a new deployment.
-    // For more background see issue 1553.
+    // Let's cache our 404'ing assets conservatively.
+    // The Cache-Control is short, and let's use the default surrogate
+    // key just in case it was a mistake.
     cacheControl(res)
     // Undo the cookie setting that CSRF sets.
     res.removeHeader('set-cookie')
diff --git a/package-lock.json b/package-lock.json
index ffb2aff60c..785d7798dc 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -135,7 +135,6 @@
         "git-diff": "^2.0.6",
         "glob": "^7.2.0",
         "graphql": "^16.3.0",
-        "heroku-client": "^3.1.0",
         "http-status-code": "^2.1.0",
         "husky": "^7.0.4",
         "japanese-characters": "^1.1.0",
@@ -10576,19 +10575,6 @@
         "node": ">=10.0.0"
       }
     },
-    "node_modules/heroku-client": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/heroku-client/-/heroku-client-3.1.0.tgz",
-      "integrity": "sha512-UfGKwUm5duzzSVI8uUXlNAE1mus6uPxmZPji4vuG1ArV5DYL1rXsZShp0OoxraWdEwYoxCUrM6KGztC68x5EZQ==",
-      "dev": true,
-      "dependencies": {
-        "is-retry-allowed": "^1.0.0",
-        "tunnel-agent": "^0.6.0"
-      },
-      "engines": {
-        "node": ">=6.0.0"
-      }
-    },
     "node_modules/hexoid": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/hexoid/-/hexoid-1.0.0.tgz",
@@ -11433,15 +11419,6 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-retry-allowed": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/is-retry-allowed/-/is-retry-allowed-1.2.0.tgz",
-      "integrity": "sha512-RUbUeKwvm3XG2VYamhJL1xFktgjvPzL0Hq8C+6yrWIswDy3BIXGqCxhxkc30N9jqK311gVU137K8Ei55/zVJRg==",
-      "dev": true,
-      "engines": {
-        "node": ">=0.10.0"
-      }
-    },
     "node_modules/is-shared-array-buffer": {
       "version": "1.0.1",
       "resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz",
@@ -21037,18 +21014,6 @@
         "node": ">=0.6.11 <=0.7.0 || >=0.7.3"
       }
     },
-    "node_modules/tunnel-agent": {
-      "version": "0.6.0",
-      "resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz",
-      "integrity": "sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=",
-      "dev": true,
-      "dependencies": {
-        "safe-buffer": "^5.0.1"
-      },
-      "engines": {
-        "node": "*"
-      }
-    },
     "node_modules/type-check": {
       "version": "0.4.0",
       "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
@@ -30703,16 +30668,6 @@
       "resolved": "https://registry.npmjs.org/helmet/-/helmet-4.6.0.tgz",
       "integrity": "sha512-HVqALKZlR95ROkrnesdhbbZJFi/rIVSoNq6f3jA/9u6MIbTsPh3xZwihjeI5+DO/2sOV6HMHooXcEOuwskHpTg=="
     },
-    "heroku-client": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/heroku-client/-/heroku-client-3.1.0.tgz",
-      "integrity": "sha512-UfGKwUm5duzzSVI8uUXlNAE1mus6uPxmZPji4vuG1ArV5DYL1rXsZShp0OoxraWdEwYoxCUrM6KGztC68x5EZQ==",
-      "dev": true,
-      "requires": {
-        "is-retry-allowed": "^1.0.0",
-        "tunnel-agent": "^0.6.0"
-      }
-    },
     "hexoid": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/hexoid/-/hexoid-1.0.0.tgz",
@@ -31292,12 +31247,6 @@
         "has-tostringtag": "^1.0.0"
       }
     },
-    "is-retry-allowed": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/is-retry-allowed/-/is-retry-allowed-1.2.0.tgz",
-      "integrity": "sha512-RUbUeKwvm3XG2VYamhJL1xFktgjvPzL0Hq8C+6yrWIswDy3BIXGqCxhxkc30N9jqK311gVU137K8Ei55/zVJRg==",
-      "dev": true
-    },
     "is-shared-array-buffer": {
       "version": "1.0.1",
       "resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz",
@@ -38575,15 +38524,6 @@
       "integrity": "sha512-1h/Lnq9yajKY2PEbBadPXj3VxsDDu844OnaAo52UVmIzIvwwtBPIuNvkjuzBlTWpfJyUbG3ez0KSBibQkj4ojg==",
       "dev": true
     },
-    "tunnel-agent": {
-      "version": "0.6.0",
-      "resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz",
-      "integrity": "sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=",
-      "dev": true,
-      "requires": {
-        "safe-buffer": "^5.0.1"
-      }
-    },
     "type-check": {
       "version": "0.4.0",
       "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
diff --git a/package.json b/package.json
index 59dba3dcf7..d4414fcf92 100644
--- a/package.json
+++ b/package.json
@@ -137,7 +137,6 @@
     "git-diff": "^2.0.6",
     "glob": "^7.2.0",
     "graphql": "^16.3.0",
-    "heroku-client": "^3.1.0",
     "http-status-code": "^2.1.0",
     "husky": "^7.0.4",
     "japanese-characters": "^1.1.0",
@@ -193,7 +192,6 @@
     "build": "next build",
     "debug": "cross-env NODE_ENV=development ENABLED_LANGUAGES='en,ja' nodemon --inspect server.mjs",
     "dev": "npm start",
-    "heroku-postbuild": "node script/early-access/clone-for-build.js && npm run build",
     "lint": "eslint '**/*.{js,mjs,ts,tsx}'",
     "lint-translation": "cross-env NODE_OPTIONS=--experimental-vm-modules TEST_TRANSLATION=true jest tests/linting/lint-files.js",
     "pa11y-ci": "pa11y-ci",
diff --git a/pages/[versionId]/[productId]/index.tsx b/pages/[versionId]/[productId]/index.tsx
index fa563d660e..dd0393ac35 100644
--- a/pages/[versionId]/[productId]/index.tsx
+++ b/pages/[versionId]/[productId]/index.tsx
@@ -45,10 +45,10 @@ function initiateArticleScripts() {
 
 type Props = {
   mainContext: MainContextT
-  productLandingContext: ProductLandingContextT
-  productGuidesContext: ProductGuidesContextT
-  tocLandingContext: TocLandingContextT
-  articleContext: ArticleContextT
+  productLandingContext?: ProductLandingContextT
+  productGuidesContext?: ProductGuidesContextT
+  tocLandingContext?: TocLandingContextT
+  articleContext?: ArticleContextT
 }
 const GlobalPage = ({
   mainContext,
@@ -57,7 +57,6 @@ const GlobalPage = ({
   tocLandingContext,
   articleContext,
 }: Props) => {
-  const { currentLayoutName, relativePath } = mainContext
   const router = useRouter()
 
   useEffect(() => {
@@ -70,30 +69,32 @@ const GlobalPage = ({
   }, [router.events])
 
   let content
-  if (currentLayoutName === 'product-landing') {
+  if (productLandingContext) {
     content = (
       <ProductLandingContext.Provider value={productLandingContext}>
         <ProductLanding />
       </ProductLandingContext.Provider>
     )
-  } else if (currentLayoutName === 'product-guides') {
+  } else if (productGuidesContext) {
     content = (
       <ProductGuidesContext.Provider value={productGuidesContext}>
         <ProductGuides />
       </ProductGuidesContext.Provider>
     )
-  } else if (relativePath?.endsWith('index.md')) {
+  } else if (tocLandingContext) {
     content = (
       <TocLandingContext.Provider value={tocLandingContext}>
         <TocLanding />
       </TocLandingContext.Provider>
     )
-  } else {
+  } else if (articleContext) {
     content = (
       <ArticleContext.Provider value={articleContext}>
         <ArticlePage />
       </ArticleContext.Provider>
     )
+  } else {
+    throw new Error('No context provided to page')
   }
 
   return <MainContext.Provider value={mainContext}>{content}</MainContext.Provider>
@@ -105,13 +106,23 @@ export const getServerSideProps: GetServerSideProps<Props> = async (context) =>
   const req = context.req as any
   const res = context.res as any
 
+  const props: Props = {
+    mainContext: getMainContext(req, res),
+  }
+  const { currentLayoutName, relativePath } = props.mainContext
+
+  // This looks a little funky, but it's so we only send one context's data to the client
+  if (currentLayoutName === 'product-landing') {
+    props.productLandingContext = getProductLandingContextFromRequest(req)
+  } else if (currentLayoutName === 'product-guides') {
+    props.productGuidesContext = getProductGuidesContextFromRequest(req)
+  } else if (relativePath?.endsWith('index.md')) {
+    props.tocLandingContext = getTocLandingContextFromRequest(req)
+  } else {
+    props.articleContext = getArticleContextFromRequest(req)
+  }
+
   return {
-    props: {
-      mainContext: getMainContext(req, res),
-      productLandingContext: getProductLandingContextFromRequest(req),
-      productGuidesContext: getProductGuidesContextFromRequest(req),
-      tocLandingContext: getTocLandingContextFromRequest(req),
-      articleContext: getArticleContextFromRequest(req),
-    },
+    props,
   }
 }
diff --git a/script/deployment/create-staging-app-name.js b/script/deployment/create-staging-app-name.js
deleted file mode 100644
index cee33514bc..0000000000
--- a/script/deployment/create-staging-app-name.js
+++ /dev/null
@@ -1,18 +0,0 @@
-import GithubSlugger from 'github-slugger'
-const slugify = GithubSlugger.slug
-
-const APP_NAME_MAX_LENGTH = 30
-
-export default function ({ prefix = '', repo, pullNumber, branch }) {
-  return (
-    `${prefix}${repo}-${pullNumber}--${slugify(branch)}`
-      // Shorten the string to the max allowed length
-      .slice(0, APP_NAME_MAX_LENGTH)
-      // Convert underscores to dashes
-      .replace(/_/g, '-')
-      // Remove trailing dashes
-      .replace(/-+$/, '')
-      // Make it all lowercase
-      .toLowerCase()
-  )
-}
diff --git a/script/deployment/deploy-to-production.js b/script/deployment/deploy-to-production.js
deleted file mode 100755
index b23482bc98..0000000000
--- a/script/deployment/deploy-to-production.js
+++ /dev/null
@@ -1,465 +0,0 @@
-#!/usr/bin/env node
-import got from 'got'
-import Heroku from 'heroku-client'
-import { setOutput } from '@actions/core'
-
-const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms))
-
-const SLEEP_INTERVAL = 5000
-const HEROKU_LOG_LINES_TO_SHOW = 25
-const DELAY_FOR_PREBOOT_SWAP = 135000 // 2:15
-
-// Allow for a few 404 (Not Found), 429 (Too Many Requests), etc. responses from
-// the semi-unreliable Heroku API when we're polling for status updates
-const ALLOWED_MISSING_RESPONSE_COUNT =
-  parseInt(process.env.ALLOWED_POLLING_FAILURES_PER_PHASE, 10) || 10
-const ALLOWABLE_ERROR_CODES = [404, 429, 500, 503]
-
-export default async function deployToProduction({
-  octokit,
-  includeDelayForPreboot = true,
-  // These parameters will only be set by Actions
-  sourceBlobUrl = null,
-  runId = null,
-}) {
-  // Start a timer so we can report how long the deployment takes
-  const startTime = Date.now()
-  const [owner, repo, branch] = ['github', 'docs-internal', 'main']
-
-  let sha
-  try {
-    const {
-      data: { sha: latestSha },
-    } = await octokit.repos.getCommit({
-      owner,
-      repo,
-      ref: branch,
-    })
-    sha = latestSha
-
-    if (!sha) {
-      throw new Error('Latest commit SHA could not be found')
-    }
-  } catch (error) {
-    console.error(`Error: ${error}`)
-    console.log(`🛑 There was an error getting latest commit.`)
-    process.exit(1)
-  }
-
-  // Put together application configuration variables
-  const isPrebuilt = !!sourceBlobUrl
-  const { DOCUBOT_REPO_PAT } = process.env
-  const appConfigVars = {
-    // Track the git branch
-    GIT_BRANCH: branch,
-    // If prebuilt: prevent the Heroku Node.js buildpack from installing devDependencies
-    NPM_CONFIG_PRODUCTION: isPrebuilt.toString(),
-    // If prebuilt: prevent the Heroku Node.js buildpack from using `npm ci` as it would
-    // delete all of the vendored "node_modules/" directory.
-    USE_NPM_INSTALL: isPrebuilt.toString(),
-    // If not prebuilt, include the PAT required for cloning the `docs-early-access` repo.
-    // Otherwise, set it to `null` to unset it from the environment for security.
-    DOCUBOT_REPO_PAT: (!isPrebuilt && DOCUBOT_REPO_PAT) || null,
-  }
-
-  const workflowRunLog = runId ? `https://github.com/${owner}/${repo}/actions/runs/${runId}` : null
-  let deploymentId = null
-  let logUrl = workflowRunLog
-
-  const appName = process.env.HEROKU_PRODUCTION_APP_NAME
-  const environment = 'production'
-  const homepageUrl = 'https://docs.github.com/'
-
-  try {
-    const title = `branch '${branch}' at commit '${sha}' in the '${environment}' environment`
-
-    console.log(`About to deploy ${title}...`)
-
-    // Kick off a pending GitHub Deployment right away, so the PR author
-    // will have instant feedback that their work is being deployed.
-    const { data: deployment } = await octokit.repos.createDeployment({
-      owner,
-      repo,
-      description: `Deploying ${title}`,
-      ref: sha,
-
-      // In the GitHub API, there can only be one active deployment per environment.
-      environment,
-
-      // The status contexts to verify against commit status checks. If you omit
-      // this parameter, GitHub verifies all unique contexts before creating a
-      // deployment. To bypass checking entirely, pass an empty array. Defaults
-      // to all unique contexts.
-      required_contexts: [],
-
-      // Do not try to merge the base branch into the feature branch
-      auto_merge: false,
-    })
-    console.log('GitHub Deployment created', deployment)
-
-    // Store this ID for later updating
-    deploymentId = deployment.id
-
-    // Set some output variables for workflow steps that run after this script
-    if (process.env.GITHUB_ACTIONS) {
-      setOutput('deploymentId', deploymentId)
-      setOutput('logUrl', logUrl)
-    }
-
-    await octokit.repos.createDeploymentStatus({
-      owner,
-      repo,
-      deployment_id: deploymentId,
-      state: 'in_progress',
-      description: 'Deploying the app...',
-      // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-      // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-      // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-      mediaType: {
-        previews: ['ant-man', 'flash'],
-      },
-    })
-    console.log('🚀 Deployment status: in_progress - Preparing to deploy the app...')
-
-    // Time to talk to Heroku...
-    const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-    let build = null
-
-    if (!sourceBlobUrl) {
-      try {
-        sourceBlobUrl = await getTarballUrl({
-          octokit,
-          owner,
-          repo,
-          sha,
-        })
-      } catch (error) {
-        throw new Error(`Failed to generate source blob URL. Error: ${error}`)
-      }
-    }
-
-    console.log('Updating Heroku app configuration variables...')
-
-    // Reconfigure environment variables
-    // https://devcenter.heroku.com/articles/platform-api-reference#config-vars-update
-    try {
-      await heroku.patch(`/apps/${appName}/config-vars`, {
-        body: appConfigVars,
-      })
-    } catch (error) {
-      announceIfHerokuIsDown(error)
-      throw new Error(`Failed to update Heroku app configuration variables. Error: ${error}`)
-    }
-
-    console.log('Reconfigured')
-    console.log('Building Heroku app...')
-
-    try {
-      build = await heroku.post(`/apps/${appName}/builds`, {
-        body: {
-          source_blob: {
-            url: sourceBlobUrl,
-          },
-        },
-      })
-    } catch (error) {
-      announceIfHerokuIsDown(error)
-      throw new Error(`Failed to create Heroku build. Error: ${error}`)
-    }
-
-    console.log('Heroku build created', build)
-
-    const buildStartTime = Date.now() // Close enough...
-    const buildId = build.id
-    logUrl = build.output_stream_url
-
-    console.log('🚀 Deployment status: in_progress - Building a new Heroku slug...')
-
-    // Poll until the Build's status changes from "pending" to "succeeded" or "failed".
-    let buildAcceptableErrorCount = 0
-    while (!build || !build.release || !build.release.id) {
-      await sleep(SLEEP_INTERVAL)
-      try {
-        build = await heroku.get(`/apps/${appName}/builds/${buildId}`)
-      } catch (error) {
-        // Allow for a few bad responses from the Heroku API
-        if (isAllowableHerokuError(error)) {
-          buildAcceptableErrorCount += 1
-          if (buildAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-            console.warn(
-              `Ignoring allowable Heroku error #${buildAcceptableErrorCount}: ${error.statusCode}`
-            )
-            continue
-          }
-        }
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to get build status. Error: ${error}`)
-      }
-
-      if (build && build.status === 'failed') {
-        throw new Error(
-          `Failed to build after ${Math.round(
-            (Date.now() - buildStartTime) / 1000
-          )} seconds. See Heroku logs for more information:\n${logUrl}`
-        )
-      }
-
-      console.log(
-        `Heroku build status: ${(build || {}).status} (after ${Math.round(
-          (Date.now() - buildStartTime) / 1000
-        )} seconds)`
-      )
-    }
-
-    console.log(
-      `Finished Heroku build after ${Math.round((Date.now() - buildStartTime) / 1000)} seconds.`,
-      build
-    )
-    console.log('Heroku release detected', build.release)
-
-    const releaseStartTime = Date.now() // Close enough...
-    const releaseId = build.release.id
-    let release = null
-
-    // Poll until the associated Release's status changes from "pending" to "succeeded" or "failed".
-    let releaseAcceptableErrorCount = 0
-    while (!release || release.status === 'pending') {
-      await sleep(SLEEP_INTERVAL)
-      try {
-        const result = await heroku.get(`/apps/${appName}/releases/${releaseId}`)
-
-        // Update the deployment status but only on the first retrieval
-        if (!release) {
-          logUrl = result.output_stream_url
-
-          console.log('Heroku Release created', result)
-
-          console.log('🚀 Deployment status: in_progress - Releasing the built Heroku slug...')
-        }
-
-        release = result
-      } catch (error) {
-        // Allow for a few bad responses from the Heroku API
-        if (isAllowableHerokuError(error)) {
-          releaseAcceptableErrorCount += 1
-          if (releaseAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-            console.warn(
-              `Ignoring allowable Heroku error #${releaseAcceptableErrorCount}: ${error.statusCode}`
-            )
-            continue
-          }
-        }
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to get release status. Error: ${error}`)
-      }
-
-      if (release && release.status === 'failed') {
-        throw new Error(
-          `Failed to release after ${Math.round(
-            (Date.now() - releaseStartTime) / 1000
-          )} seconds. See Heroku logs for more information:\n${logUrl}`
-        )
-      }
-
-      console.log(
-        `Release status: ${(release || {}).status} (after ${Math.round(
-          (Date.now() - releaseStartTime) / 1000
-        )} seconds)`
-      )
-    }
-
-    console.log(
-      `Finished Heroku release after ${Math.round(
-        (Date.now() - releaseStartTime) / 1000
-      )} seconds.`,
-      release
-    )
-
-    // Monitor dyno state for this release to ensure it reaches "up" rather than crashing.
-    // This will help us catch issues with faulty startup code and/or the package manifest.
-    const dynoBootStartTime = Date.now()
-    console.log('Checking Heroku dynos...')
-    logUrl = workflowRunLog
-
-    console.log('🚀 Deployment status: in_progress - Monitoring the Heroku dyno start-up...')
-
-    // Keep checking while there are still dynos in non-terminal states
-    let newDynos = []
-    let dynoAcceptableErrorCount = 0
-    while (newDynos.length === 0 || newDynos.some((dyno) => dyno.state === 'starting')) {
-      await sleep(SLEEP_INTERVAL)
-      try {
-        const dynoList = await heroku.get(`/apps/${appName}/dynos`)
-        const dynosForThisRelease = dynoList.filter((dyno) => dyno.release.id === releaseId)
-
-        // To track them afterward
-        newDynos = dynosForThisRelease
-
-        console.log(
-          `Dyno states: ${JSON.stringify(newDynos.map((dyno) => dyno.state))} (after ${Math.round(
-            (Date.now() - dynoBootStartTime) / 1000
-          )} seconds)`
-        )
-      } catch (error) {
-        // Allow for a few bad responses from the Heroku API
-        if (isAllowableHerokuError(error)) {
-          dynoAcceptableErrorCount += 1
-          if (dynoAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-            console.warn(
-              `Ignoring allowable Heroku error #${dynoAcceptableErrorCount}: ${error.statusCode}`
-            )
-            continue
-          }
-        }
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to find dynos for this release. Error: ${error}`)
-      }
-    }
-
-    const crashedDynos = newDynos.filter((dyno) => ['crashed', 'restarting'].includes(dyno.state))
-    const runningDynos = newDynos.filter((dyno) => dyno.state === 'up')
-
-    // If any dynos crashed on start-up, fail the deployment
-    if (crashedDynos.length > 0) {
-      const errorMessage = `At least ${crashedDynos.length} Heroku dyno(s) crashed on start-up!`
-
-      console.error(errorMessage)
-
-      // Attempt to dump some of the Heroku log here for debugging
-      try {
-        const logSession = await heroku.post(`/apps/${appName}/log-sessions`, {
-          body: {
-            dyno: crashedDynos[0].name,
-            lines: HEROKU_LOG_LINES_TO_SHOW,
-            tail: false,
-          },
-        })
-
-        logUrl = logSession.logplex_url
-
-        const logText = await got(logUrl).text()
-        console.error(
-          `Here are the last ${HEROKU_LOG_LINES_TO_SHOW} lines of the Heroku log:\n\n${logText}`
-        )
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        // Don't fail because of this error
-        console.error(`Failed to retrieve the Heroku logs for the crashed dynos. Error: ${error}`)
-      }
-
-      throw new Error(errorMessage)
-    }
-
-    console.log(
-      `At least ${runningDynos.length} Heroku dyno(s) are ready after ${Math.round(
-        (Date.now() - dynoBootStartTime) / 1000
-      )} seconds.`
-    )
-
-    // IMPORTANT:
-    // If Heroku Preboot is enabled, then there is an additional delay of at
-    // least 2 minutes before the new dynos are swapped into active serving.
-    // If we move off Heroku in the future, this should be revisited and
-    // updated/removed as relevant to align with the new hosting platform.
-    if (includeDelayForPreboot) {
-      console.log(`Waiting for Heroku Preboot to swap dynos (${DELAY_FOR_PREBOOT_SWAP} ms)...`)
-      await sleep(DELAY_FOR_PREBOOT_SWAP)
-
-      // TODO:
-      // Is there a faster alternative than this arbitrary delay? For example,
-      // is there some Heroku API we can query to see when this release is
-      // considered to be the live one, or when the old dynos are shut down?
-    } else {
-      console.warn(
-        '⚠️ Bypassing the wait for Heroku Preboot....\nPlease understand that your changes will not be visible for at least another 2 minutes!'
-      )
-    }
-
-    // Report success!
-    const successMessage = `Deployment succeeded after ${Math.round(
-      (Date.now() - startTime) / 1000
-    )} seconds.`
-    console.log(successMessage)
-
-    await octokit.repos.createDeploymentStatus({
-      owner,
-      repo,
-      deployment_id: deploymentId,
-      state: 'success',
-      description: successMessage,
-      ...(logUrl && { log_url: logUrl }),
-      environment_url: homepageUrl,
-      // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-      // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-      // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-      mediaType: {
-        previews: ['ant-man', 'flash'],
-      },
-    })
-
-    console.log(`🚀 Deployment status: success - ${successMessage}`)
-    console.log(`Visit the newly deployed app at: ${homepageUrl}`)
-  } catch (error) {
-    // Report failure!
-    const failureMessage = `Deployment failed after ${Math.round(
-      (Date.now() - startTime) / 1000
-    )} seconds. See logs for more information.`
-    console.error(failureMessage)
-
-    try {
-      if (deploymentId) {
-        await octokit.repos.createDeploymentStatus({
-          owner,
-          repo,
-          deployment_id: deploymentId,
-          state: 'error',
-          description: failureMessage,
-          ...(logUrl && { log_url: logUrl }),
-          environment_url: homepageUrl,
-          // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-          // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-          // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-          mediaType: {
-            previews: ['ant-man', 'flash'],
-          },
-        })
-
-        console.log(
-          `🚀 Deployment status: error - ${failureMessage}` + (logUrl ? ` Logs: ${logUrl}` : '')
-        )
-      }
-    } catch (error) {
-      console.error(`Failed to finalize GitHub Deployment Status as a failure. Error: ${error}`)
-    }
-
-    // Re-throw the error to bubble up
-    throw error
-  }
-}
-
-async function getTarballUrl({ octokit, owner, repo, sha }) {
-  // Get a URL for the tarballed source code bundle
-  const {
-    headers: { location: tarballUrl },
-  } = await octokit.repos.downloadTarballArchive({
-    owner,
-    repo,
-    ref: sha,
-    // Override the underlying `node-fetch` module's `redirect` option
-    // configuration to prevent automatically following redirects.
-    request: {
-      redirect: 'manual',
-    },
-  })
-  return tarballUrl
-}
-
-function isAllowableHerokuError(error) {
-  return error && ALLOWABLE_ERROR_CODES.includes(error.statusCode)
-}
-
-function announceIfHerokuIsDown(error) {
-  if (error && error.statusCode === 503) {
-    console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/')
-  }
-}
diff --git a/script/deployment/deploy-to-staging.js b/script/deployment/deploy-to-staging.js
deleted file mode 100644
index 5e3df9a09b..0000000000
--- a/script/deployment/deploy-to-staging.js
+++ /dev/null
@@ -1,680 +0,0 @@
-#!/usr/bin/env node
-import got from 'got'
-import Heroku from 'heroku-client'
-import { setOutput } from '@actions/core'
-import createStagingAppName from './create-staging-app-name.js'
-
-// Equivalent of the 'await-sleep' module without the install
-const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms))
-
-const SLEEP_INTERVAL = 5000
-const HEROKU_LOG_LINES_TO_SHOW = 25
-
-// Allow for a few 404 (Not Found), 429 (Too Many Requests), etc. responses from
-// the semi-unreliable Heroku API when we're polling for status updates
-const ALLOWED_MISSING_RESPONSE_COUNT =
-  parseInt(process.env.ALLOWED_POLLING_FAILURES_PER_PHASE, 10) || 10
-const ALLOWABLE_ERROR_CODES = [404, 429, 500, 503]
-
-export default async function deployToStaging({
-  octokit,
-  pullRequest,
-  forceRebuild = false,
-  // These parameters will only be set by Actions
-  sourceBlobUrl = null,
-  runId = null,
-}) {
-  // Start a timer so we can report how long the deployment takes
-  const startTime = Date.now()
-
-  // Extract some important properties from the PR
-  const {
-    number: pullNumber,
-    base: {
-      repo: {
-        name: repo,
-        owner: { login: owner },
-      },
-    },
-    state,
-    head: { ref: branch, sha },
-    user: author,
-  } = pullRequest
-
-  // Verify the PR is still open
-  if (state !== 'open') {
-    throw new Error(`This pull request is not open. State is: '${state}'`)
-  }
-
-  // Put together application configuration variables
-  const isPrivateRepo = owner === 'github' && repo === 'docs-internal'
-  const isPrebuilt = !!sourceBlobUrl
-  const { DOCUBOT_REPO_PAT, HYDRO_ENDPOINT, HYDRO_SECRET } = process.env
-  const appConfigVars = {
-    // Track the git branch
-    GIT_BRANCH: branch,
-    // If prebuilt: prevent the Heroku Node.js buildpack from installing devDependencies
-    NPM_CONFIG_PRODUCTION: isPrebuilt.toString(),
-    // If prebuilt: prevent the Heroku Node.js buildpack from using `npm ci` as it would
-    // delete all of the vendored "node_modules/" directory.
-    USE_NPM_INSTALL: isPrebuilt.toString(),
-    // IMPORTANT: This secret should only be set in the private repo!
-    // If not prebuilt, include the PAT required for cloning the `docs-early-access` repo.
-    // Otherwise, set it to `null` to unset it from the environment for security.
-    DOCUBOT_REPO_PAT: (isPrivateRepo && !isPrebuilt && DOCUBOT_REPO_PAT) || null,
-    // IMPORTANT: These secrets should only be set in the private repo!
-    // These are required for Hydro event tracking
-    ...(isPrivateRepo && HYDRO_ENDPOINT && HYDRO_SECRET && { HYDRO_ENDPOINT, HYDRO_SECRET }),
-  }
-
-  const workflowRunLog = runId ? `https://github.com/${owner}/${repo}/actions/runs/${runId}` : null
-  let deploymentId = null
-  let logUrl = workflowRunLog
-  let appIsNewlyCreated = false
-
-  const appName = createStagingAppName({ repo, pullNumber, branch })
-  const environment = appName
-  const homepageUrl = `https://${appName}.herokuapp.com/`
-
-  try {
-    const title = `branch '${branch}' at commit '${sha}' in the '${environment}' staging environment`
-
-    console.log(`About to deploy ${title}...`)
-
-    // Kick off a pending GitHub Deployment right away, so the PR author
-    // will have instant feedback that their work is being deployed.
-    const { data: deployment } = await octokit.repos.createDeployment({
-      owner,
-      repo,
-
-      description: `Deploying ${title}`,
-
-      // Use a commit SHA instead of a branch name as the ref for more precise
-      // feedback, and also because the branch may have already been deleted.
-      ref: sha,
-
-      // In the GitHub API, there can only be one active deployment per environment.
-      // For our many staging apps, we must use the unique appName as the environment.
-      environment,
-
-      // The status contexts to verify against commit status checks. If you omit
-      // this parameter, GitHub verifies all unique contexts before creating a
-      // deployment. To bypass checking entirely, pass an empty array. Defaults
-      // to all unique contexts.
-      required_contexts: [],
-
-      // Do not try to merge the base branch into the feature branch
-      auto_merge: false,
-    })
-    console.log('GitHub Deployment created', deployment)
-
-    // Store this ID for later updating
-    deploymentId = deployment.id
-
-    // Set some output variables for workflow steps that run after this script
-    if (process.env.GITHUB_ACTIONS) {
-      setOutput('deploymentId', deploymentId)
-      setOutput('logUrl', logUrl)
-    }
-
-    await octokit.repos.createDeploymentStatus({
-      owner,
-      repo,
-      deployment_id: deploymentId,
-      state: 'in_progress',
-      description: 'Deploying the app...',
-      // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-      // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-      // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-      mediaType: {
-        previews: ['ant-man', 'flash'],
-      },
-    })
-    console.log('🚀 Deployment status: in_progress - Preparing to deploy the app...')
-
-    // Time to talk to Heroku...
-    const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-    let appSetup = null
-    let build = null
-
-    // Is there already a Heroku App for this PR?
-    let appExists = true
-    try {
-      await heroku.get(`/apps/${appName}`)
-    } catch (error) {
-      announceIfHerokuIsDown(error)
-      appExists = false
-    }
-
-    // If there is an existing app but we want to forcibly rebuild, delete the app first
-    if (appExists && forceRebuild) {
-      console.log('🚀 Deployment status: in_progress - Destroying existing Heroku app...')
-
-      try {
-        await heroku.delete(`/apps/${appName}`)
-        appExists = false
-
-        console.log(`Heroku app '${appName}' deleted for forced rebuild`)
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        throw new Error(
-          `Failed to delete Heroku app '${appName}' for forced rebuild. Error: ${error}`
-        )
-      }
-    }
-
-    if (!sourceBlobUrl) {
-      try {
-        sourceBlobUrl = await getTarballUrl({
-          octokit,
-          owner,
-          repo,
-          sha,
-        })
-      } catch (error) {
-        throw new Error(`Failed to generate source blob URL. Error: ${error}`)
-      }
-    }
-
-    // If an app does not exist, create one!
-    // This action will also trigger a build as a by-product.
-    if (!appExists) {
-      appIsNewlyCreated = true
-
-      console.log(`Heroku app '${appName}' does not exist. Creating a new AppSetup...`)
-
-      console.log('🚀 Deployment status: in_progress - Creating a new Heroku app...')
-
-      const appSetupStartTime = Date.now()
-      try {
-        appSetup = await heroku.post('/app-setups', {
-          body: {
-            app: {
-              name: appName,
-            },
-            source_blob: {
-              url: sourceBlobUrl,
-            },
-
-            // Pass some environment variables to staging apps via Heroku
-            // config variables.
-            overrides: {
-              // AppSetup API cannot handle `null` values for config vars
-              env: removeEmptyProperties(appConfigVars),
-            },
-          },
-        })
-        console.log('Heroku AppSetup created', appSetup)
-
-        // This probably will not be available yet
-        build = appSetup.build
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to create Heroku app '${appName}'. Error: ${error}`)
-      }
-
-      // Add PR author (if staff) as a collaborator on the new staging app
-      try {
-        if (author.site_admin === true) {
-          await heroku.post(`/apps/${appName}/collaborators`, {
-            body: {
-              user: `${author.login}@github.com`,
-              // We don't want an email invitation for every new staging app
-              silent: true,
-            },
-          })
-          console.log(`Added PR author @${author.login} as a Heroku app collaborator`)
-        }
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        // It's fine if this fails, it shouldn't block the app from deploying!
-        console.warn(
-          `Warning: failed to add PR author as a Heroku app collaborator. Error: ${error}`
-        )
-      }
-
-      // A new Build is created as a by-product of creating an AppSetup.
-      // Poll until there is a Build object attached to the AppSetup.
-      let setupAcceptableErrorCount = 0
-      while (!appSetup || !build || !build.id) {
-        await sleep(SLEEP_INTERVAL)
-        try {
-          appSetup = await heroku.get(`/app-setups/${appSetup.id}`)
-          build = appSetup.build
-        } catch (error) {
-          // Allow for a few bad responses from the Heroku API
-          if (isAllowableHerokuError(error)) {
-            setupAcceptableErrorCount += 1
-            if (setupAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-              console.warn(
-                `Ignoring allowable Heroku error #${setupAcceptableErrorCount}: ${error.statusCode}`
-              )
-              continue
-            }
-          }
-          announceIfHerokuIsDown(error)
-          throw new Error(`Failed to get AppSetup status. Error: ${error}`)
-        }
-
-        if (appSetup && appSetup.status === 'failed') {
-          const manifestErrors = appSetup.manifest_errors || []
-          const hasManifestErrors = Array.isArray(manifestErrors) && manifestErrors.length > 0
-          const manifestErrorMessage = hasManifestErrors
-            ? `\nManifest errors:\n - ${manifestErrors.join('\n - ')}`
-            : ''
-          throw new Error(
-            `Failed to setup app after ${Math.round(
-              (Date.now() - appSetupStartTime) / 1000
-            )} seconds.
-Reason: ${appSetup.failure_message}${manifestErrorMessage}
-See Heroku logs for more information:\n${logUrl}`
-          )
-        }
-
-        console.log(
-          `AppSetup status: ${appSetup.status} (after ${Math.round(
-            (Date.now() - appSetupStartTime) / 1000
-          )} seconds)`
-        )
-      }
-
-      console.log('Heroku AppSetup finished', appSetup)
-      console.log('Heroku build detected', build)
-    } else {
-      // If the app does exist, just manually trigger a new build
-      console.log(`Heroku app '${appName}' already exists.`)
-
-      console.log('Updating Heroku app configuration variables...')
-
-      // Reconfigure environment variables
-      // https://devcenter.heroku.com/articles/platform-api-reference#config-vars-update
-      try {
-        await heroku.patch(`/apps/${appName}/config-vars`, {
-          body: appConfigVars,
-        })
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to update Heroku app configuration variables. Error: ${error}`)
-      }
-
-      console.log('Reconfigured')
-      console.log('Building Heroku app...')
-
-      try {
-        build = await heroku.post(`/apps/${appName}/builds`, {
-          body: {
-            source_blob: {
-              url: sourceBlobUrl,
-            },
-          },
-        })
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to create Heroku build. Error: ${error}`)
-      }
-
-      console.log('Heroku build created', build)
-    }
-
-    const buildStartTime = Date.now() // Close enough...
-    const buildId = build.id
-    logUrl = build.output_stream_url
-
-    console.log('🚀 Deployment status: in_progress - Building a new Heroku slug...')
-
-    // Poll until the Build's status changes from "pending" to "succeeded" or "failed".
-    let buildAcceptableErrorCount = 0
-    while (!build || !build.release || !build.release.id) {
-      await sleep(SLEEP_INTERVAL)
-      try {
-        build = await heroku.get(`/apps/${appName}/builds/${buildId}`)
-      } catch (error) {
-        // Allow for a few bad responses from the Heroku API
-        if (isAllowableHerokuError(error)) {
-          buildAcceptableErrorCount += 1
-          if (buildAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-            console.warn(
-              `Ignoring allowable Heroku error #${buildAcceptableErrorCount}: ${error.statusCode}`
-            )
-            continue
-          }
-        }
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to get build status. Error: ${error}`)
-      }
-
-      if (build && build.status === 'failed') {
-        throw new Error(
-          `Failed to build after ${Math.round(
-            (Date.now() - buildStartTime) / 1000
-          )} seconds. See Heroku logs for more information:\n${logUrl}`
-        )
-      }
-
-      console.log(
-        `Heroku build status: ${(build || {}).status} (after ${Math.round(
-          (Date.now() - buildStartTime) / 1000
-        )} seconds)`
-      )
-    }
-
-    console.log(
-      `Finished Heroku build after ${Math.round((Date.now() - buildStartTime) / 1000)} seconds.`,
-      build
-    )
-    console.log('Heroku release detected', build.release)
-
-    const releaseStartTime = Date.now() // Close enough...
-    let releaseId = build.release.id
-    let release = null
-
-    // Poll until the associated Release's status changes from "pending" to "succeeded" or "failed".
-    let releaseAcceptableErrorCount = 0
-    while (!release || release.status === 'pending') {
-      await sleep(SLEEP_INTERVAL)
-      try {
-        const result = await heroku.get(`/apps/${appName}/releases/${releaseId}`)
-
-        // Update the deployment status but only on the first retrieval
-        if (!release) {
-          logUrl = result.output_stream_url
-
-          console.log('Heroku Release created', result)
-
-          console.log('🚀 Deployment status: in_progress - Releasing the built Heroku slug...')
-        }
-
-        release = result
-      } catch (error) {
-        // Allow for a few bad responses from the Heroku API
-        if (isAllowableHerokuError(error)) {
-          releaseAcceptableErrorCount += 1
-          if (releaseAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-            console.warn(
-              `Ignoring allowable Heroku error #${releaseAcceptableErrorCount}: ${error.statusCode}`
-            )
-            continue
-          }
-        }
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to get release status. Error: ${error}`)
-      }
-
-      if (release && release.status === 'failed') {
-        throw new Error(
-          `Failed to release after ${Math.round(
-            (Date.now() - releaseStartTime) / 1000
-          )} seconds. See Heroku logs for more information:\n${logUrl}`
-        )
-      }
-
-      console.log(
-        `Release status: ${(release || {}).status} (after ${Math.round(
-          (Date.now() - releaseStartTime) / 1000
-        )} seconds)`
-      )
-    }
-
-    console.log(
-      `Finished Heroku release after ${Math.round(
-        (Date.now() - releaseStartTime) / 1000
-      )} seconds.`,
-      release
-    )
-
-    // Monitor dyno state for this release to ensure it reaches "up" rather than crashing.
-    // This will help us catch issues with faulty startup code and/or the package manifest.
-    const dynoBootStartTime = Date.now()
-    console.log('Checking Heroku dynos...')
-    logUrl = workflowRunLog
-
-    console.log('🚀 Deployment status: in_progress - Monitoring the Heroku dyno start-up...')
-
-    // Keep checking while there are still dynos in non-terminal states
-    let newDynos = []
-    let dynoAcceptableErrorCount = 0
-    while (newDynos.length === 0 || newDynos.some((dyno) => dyno.state === 'starting')) {
-      await sleep(SLEEP_INTERVAL)
-      try {
-        const dynoList = await heroku.get(`/apps/${appName}/dynos`)
-        const dynosForThisRelease = dynoList.filter((dyno) => dyno.release.id === releaseId)
-
-        // To track them afterward
-        newDynos = dynosForThisRelease
-
-        // Dynos for this release OR a newer release
-        const relevantDynos = dynoList.filter((dyno) => dyno.release.version >= release.version)
-
-        // If this Heroku app was just newly created, often a secondary release
-        // is requested to enable automatically managed SSL certificates. The
-        // release description will read:
-        //   "Enable allow-multiple-sni-endpoints feature"
-        //
-        // If that is the case, we need to update to monitor that secondary
-        // release instead.
-        if (relevantDynos.length > 0 && dynosForThisRelease.length === 0) {
-          // If the app is NOT newly created, fail fast!
-          if (!appIsNewlyCreated) {
-            throw new Error('The dynos for this release disappeared unexpectedly')
-          }
-
-          // Check for the secondary release
-          let nextRelease = null
-          try {
-            nextRelease = await heroku.get(`/apps/${appName}/releases/${release.version + 1}`)
-          } catch (error) {
-            announceIfHerokuIsDown(error)
-            throw new Error(
-              `Could not find a secondary release to explain the disappearing dynos. Error: ${error}`
-            )
-          }
-
-          if (nextRelease) {
-            if (nextRelease.description === 'Enable allow-multiple-sni-endpoints feature') {
-              // Track dynos for the next release instead
-              release = nextRelease
-              releaseId = nextRelease.id
-
-              console.warn('Switching to monitor secondary release...')
-
-              // Allow the loop to repeat to fetch the dynos for the secondary release
-            } else {
-              // Otherwise, assume another release replaced this one but it
-              // PROBABLY would've succeeded...?
-              newDynos.forEach((dyno) => {
-                dyno.state = 'up'
-              })
-            }
-          }
-          // else just keep monitoring and hope for the best
-        }
-
-        console.log(
-          `Dyno states: ${JSON.stringify(newDynos.map((dyno) => dyno.state))} (after ${Math.round(
-            (Date.now() - dynoBootStartTime) / 1000
-          )} seconds)`
-        )
-      } catch (error) {
-        // Allow for a few bad responses from the Heroku API
-        if (isAllowableHerokuError(error)) {
-          dynoAcceptableErrorCount += 1
-          if (dynoAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) {
-            console.warn(
-              `Ignoring allowable Heroku error #${dynoAcceptableErrorCount}: ${error.statusCode}`
-            )
-            continue
-          }
-        }
-        announceIfHerokuIsDown(error)
-        throw new Error(`Failed to find dynos for this release. Error: ${error}`)
-      }
-    }
-
-    const crashedDynos = newDynos.filter((dyno) => ['crashed', 'restarting'].includes(dyno.state))
-    const runningDynos = newDynos.filter((dyno) => dyno.state === 'up')
-
-    // If any dynos crashed on start-up, fail the deployment
-    if (crashedDynos.length > 0) {
-      const errorMessage = `At least ${crashedDynos.length} Heroku dyno(s) crashed on start-up!`
-
-      console.error(errorMessage)
-
-      // Attempt to dump some of the Heroku log here for debugging
-      try {
-        const logSession = await heroku.post(`/apps/${appName}/log-sessions`, {
-          body: {
-            dyno: crashedDynos[0].name,
-            lines: HEROKU_LOG_LINES_TO_SHOW,
-            tail: false,
-          },
-        })
-
-        logUrl = logSession.logplex_url
-
-        const logText = await got(logUrl).text()
-        console.error(
-          `Here are the last ${HEROKU_LOG_LINES_TO_SHOW} lines of the Heroku log:\n\n${logText}`
-        )
-      } catch (error) {
-        announceIfHerokuIsDown(error)
-        // Don't fail because of this error
-        console.error(`Failed to retrieve the Heroku logs for the crashed dynos. Error: ${error}`)
-      }
-
-      throw new Error(errorMessage)
-    }
-
-    console.log(
-      `At least ${runningDynos.length} Heroku dyno(s) are ready after ${Math.round(
-        (Date.now() - dynoBootStartTime) / 1000
-      )} seconds.`
-    )
-
-    // Send a series of requests to trigger the server warmup routines
-    console.log('🚀 Deployment status: in_progress - Triggering server warmup routines...')
-
-    const warmupStartTime = Date.now()
-    console.log(`Making warmup requests to: ${homepageUrl}`)
-    try {
-      await got(homepageUrl, {
-        timeout: 10000, // Maximum 10 second timeout per request
-        retry: {
-          limit: 7, // About 2 minutes 7 seconds of delay, plus active request time for 8 requests
-          statusCodes: [404, 421].concat(got.defaults.options.retry.statusCodes), // prepend extras
-        },
-        hooks: {
-          beforeRetry: [
-            (options, error = {}, retryCount = '?') => {
-              const statusCode = error.statusCode || (error.response || {}).statusCode || -1
-              console.log(
-                `Retrying after warmup request attempt #${retryCount} (${statusCode}) after ${Math.round(
-                  (Date.now() - warmupStartTime) / 1000
-                )} seconds...`
-              )
-            },
-          ],
-        },
-      })
-      console.log(
-        `Warmup requests passed after ${Math.round((Date.now() - warmupStartTime) / 1000)} seconds`
-      )
-    } catch (error) {
-      throw new Error(
-        `Warmup requests failed after ${Math.round(
-          (Date.now() - warmupStartTime) / 1000
-        )} seconds. Error: ${error}`
-      )
-    }
-
-    // Report success!
-    const successMessage = `Deployment succeeded after ${Math.round(
-      (Date.now() - startTime) / 1000
-    )} seconds.`
-    console.log(successMessage)
-
-    await octokit.repos.createDeploymentStatus({
-      owner,
-      repo,
-      deployment_id: deploymentId,
-      state: 'success',
-      description: successMessage,
-      ...(logUrl && { log_url: logUrl }),
-      environment_url: homepageUrl,
-      // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-      // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-      // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-      mediaType: {
-        previews: ['ant-man', 'flash'],
-      },
-    })
-
-    console.log(`🚀 Deployment status: success - ${successMessage}`)
-    console.log(`Visit the newly deployed app at: ${homepageUrl}`)
-  } catch (error) {
-    // Report failure!
-    const failureMessage = `Deployment failed after ${Math.round(
-      (Date.now() - startTime) / 1000
-    )} seconds. See logs for more information.`
-    console.error(failureMessage)
-
-    try {
-      if (deploymentId) {
-        await octokit.repos.createDeploymentStatus({
-          owner,
-          repo,
-          deployment_id: deploymentId,
-          state: 'error',
-          description: failureMessage,
-          ...(logUrl && { log_url: logUrl }),
-          environment_url: homepageUrl,
-          // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-          // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-          // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-          mediaType: {
-            previews: ['ant-man', 'flash'],
-          },
-        })
-
-        console.log(
-          `🚀 Deployment status: error - ${failureMessage}` + (logUrl ? ` Logs: ${logUrl}` : '')
-        )
-      }
-    } catch (error) {
-      console.error(`Failed to finalize GitHub DeploymentStatus as a failure. Error: ${error}`)
-    }
-
-    // Re-throw the error to bubble up
-    throw error
-  }
-}
-
-async function getTarballUrl({ octokit, owner, repo, sha }) {
-  // Get a URL for the tarballed source code bundle
-  const {
-    headers: { location: tarballUrl },
-  } = await octokit.repos.downloadTarballArchive({
-    owner,
-    repo,
-    ref: sha,
-    // Override the underlying `node-fetch` module's `redirect` option
-    // configuration to prevent automatically following redirects.
-    request: {
-      redirect: 'manual',
-    },
-  })
-  return tarballUrl
-}
-
-function isAllowableHerokuError(error) {
-  return error && ALLOWABLE_ERROR_CODES.includes(error.statusCode)
-}
-
-function announceIfHerokuIsDown(error) {
-  if (error && error.statusCode === 503) {
-    console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/')
-  }
-}
-
-function removeEmptyProperties(obj) {
-  return Object.fromEntries(Object.entries(obj).filter(([key, val]) => val != null))
-}
diff --git a/script/deployment/parse-pr-url.js b/script/deployment/parse-pr-url.js
deleted file mode 100644
index af7f876dff..0000000000
--- a/script/deployment/parse-pr-url.js
+++ /dev/null
@@ -1,21 +0,0 @@
-#!/usr/bin/env node
-const USERNAME_FORMAT = '([A-Za-z0-9-]+)'
-const REPO_NAME_FORMAT = '([A-Za-z0-9._-]+)'
-const PR_NUMBER_FORMAT = '(\\d+)'
-
-const ALLOWED_PR_URL_FORMAT = new RegExp(
-  '^' +
-    '[\'"]?' +
-    `https://github\\.com/${USERNAME_FORMAT}/${REPO_NAME_FORMAT}/pull/${PR_NUMBER_FORMAT}` +
-    '[\'"]?' +
-    '$'
-)
-
-export default function parsePullRequestUrl(prUrl) {
-  const [, /* fullMatch */ owner, repo, pr] = (prUrl || '').match(ALLOWED_PR_URL_FORMAT) || []
-  return {
-    owner,
-    repo,
-    pullNumber: parseInt(pr, 10) || undefined,
-  }
-}
diff --git a/script/early-access/clone-for-build.js b/script/early-access/clone-for-build.js
deleted file mode 100755
index 5a2be19625..0000000000
--- a/script/early-access/clone-for-build.js
+++ /dev/null
@@ -1,140 +0,0 @@
-#!/usr/bin/env node
-
-// [start-readme]
-//
-// This script is run as a postbuild script during staging and deployments on Heroku. It clones a branch
-// in the early-access repo that matches the current branch in the docs repo; if one can't be found, it
-// clones the `main` branch.
-//
-// [end-readme]
-
-import dotenv from 'dotenv'
-import { execSync } from 'child_process'
-import rimraf from 'rimraf'
-import fs from 'fs'
-import path from 'path'
-import os from 'os'
-
-dotenv.config()
-const {
-  DOCUBOT_REPO_PAT,
-  HEROKU_PRODUCTION_APP,
-  GIT_BRANCH, // Set by Actions and/or the deployer with the name of the docs-internal branch
-} = process.env
-
-// Exit if PAT is not found
-if (!DOCUBOT_REPO_PAT) {
-  console.log('Skipping early access, not authorized')
-  process.exit(0)
-}
-
-const EA_PRODUCTION_BRANCH = 'main'
-
-// If a branch name is not provided in the environment, attempt to get
-// the local branch name; or default to 'main'
-let currentBranch = (GIT_BRANCH || '').replace(/^refs\/heads\//, '')
-if (!currentBranch) {
-  try {
-    currentBranch = execSync('git branch --show-current').toString()
-  } catch (err) {
-    // Ignore but log
-    console.warn('Error checking for local branch:', err.message)
-  }
-}
-if (!currentBranch) {
-  currentBranch = EA_PRODUCTION_BRANCH
-}
-
-// Early Access details
-const earlyAccessOwner = 'github'
-const earlyAccessRepoName = 'docs-early-access'
-const earlyAccessDirName = 'early-access'
-const earlyAccessFullRepo = `https://${DOCUBOT_REPO_PAT}@github.com/${earlyAccessOwner}/${earlyAccessRepoName}`
-
-// On our Azure self-hosted runners, os.tmpdir() doesn't work reliably. On Heroku, os.homedir doesn't work reliably.
-const earlyAccessCloningParentDir = process.env.CI ? os.homedir() : os.tmpdir()
-const earlyAccessCloningDir = path.join(earlyAccessCloningParentDir, earlyAccessRepoName)
-
-const destinationDirNames = ['content', 'data', 'assets/images']
-const destinationDirsMap = destinationDirNames.reduce((map, dirName) => {
-  map[dirName] = path.join(process.cwd(), dirName, earlyAccessDirName)
-  return map
-}, {})
-
-// Production vs. staging environment
-// TODO test that this works as expected
-const environment = HEROKU_PRODUCTION_APP ? 'production' : 'staging'
-
-// Early access branch to clone
-let earlyAccessBranch = HEROKU_PRODUCTION_APP ? EA_PRODUCTION_BRANCH : currentBranch
-
-// Confirm that the branch exists in the remote
-let branchExists = execSync(
-  `git ls-remote --heads ${earlyAccessFullRepo} ${earlyAccessBranch}`
-).toString()
-
-// If the branch did NOT exist, try checking for the default branch instead
-if (!branchExists && earlyAccessBranch !== EA_PRODUCTION_BRANCH) {
-  console.warn(
-    `The branch '${earlyAccessBranch}' was not found in ${earlyAccessOwner}/${earlyAccessRepoName}!`
-  )
-  console.warn(`Attempting the default branch ${EA_PRODUCTION_BRANCH} instead...`)
-
-  earlyAccessBranch = EA_PRODUCTION_BRANCH
-  branchExists = execSync(
-    `git ls-remote --heads ${earlyAccessFullRepo} ${earlyAccessBranch}`
-  ).toString()
-}
-
-// If no suitable branch was found, bail out now
-if (!branchExists) {
-  console.error(
-    `The branch '${earlyAccessBranch}' was not found in ${earlyAccessOwner}/${earlyAccessRepoName}!`
-  )
-  console.error('Exiting!')
-  process.exit(1)
-}
-
-// Remove any previously cloned copies of the early access repo
-rimraf.sync(earlyAccessCloningDir)
-
-// Clone the repo
-console.log(`Setting up: ${earlyAccessCloningDir}`)
-execSync(
-  `git clone --single-branch --branch ${earlyAccessBranch} ${earlyAccessFullRepo} ${earlyAccessRepoName}`,
-  {
-    cwd: earlyAccessCloningParentDir,
-  }
-)
-console.log(`Using early-access ${environment} branch: '${earlyAccessBranch}'`)
-
-// Remove all existing early access directories from this repo
-destinationDirNames.forEach((key) => rimraf.sync(destinationDirsMap[key]))
-
-// Move the latest early access source directories into this repo
-destinationDirNames.forEach((dirName) => {
-  const sourceDir = path.join(earlyAccessCloningDir, dirName)
-  const destDir = destinationDirsMap[dirName]
-
-  // If the source directory doesn't exist, skip it
-  if (!fs.existsSync(sourceDir)) {
-    console.warn(`Early access directory '${dirName}' does not exist. Skipping...`)
-    return
-  }
-
-  // Ensure the base directory exists
-  fs.mkdirSync(path.join(process.cwd(), dirName), { recursive: true })
-
-  // Move the directory from the cloned source to the destination
-  fs.renameSync(sourceDir, destDir)
-
-  // Confirm the newly moved directory exist
-  if (fs.existsSync(destDir)) {
-    console.log(`Successfully moved early access directory '${dirName}' into this repo`)
-  } else {
-    throw new Error(`Failed to move early access directory '${dirName}'!`)
-  }
-})
-
-// Remove the source content again for good hygiene
-rimraf.sync(earlyAccessCloningDir)
diff --git a/script/ping-staging-apps.js b/script/ping-staging-apps.js
deleted file mode 100755
index d919013597..0000000000
--- a/script/ping-staging-apps.js
+++ /dev/null
@@ -1,41 +0,0 @@
-#!/usr/bin/env node
-
-// [start-readme]
-//
-// This script finds all Heroku staging apps and pings them to make sure they're always "warmed" and responsive to requests.
-//
-// [end-readme]
-
-import dotenv from 'dotenv'
-import assert from 'assert'
-import got from 'got'
-import { chain } from 'lodash-es'
-import chalk from 'chalk'
-import Heroku from 'heroku-client'
-
-dotenv.config()
-
-assert(process.env.HEROKU_API_TOKEN)
-
-const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-
-main()
-
-async function main() {
-  const apps = chain(await heroku.get('/apps'))
-    .orderBy('name')
-    .value()
-
-  async function ping(app) {
-    // ?warmup param has no effect but makes it easier to find these requests in the logs
-    const url = `https://${app.name}.herokuapp.com/en?warmup`
-    try {
-      const response = await got(url)
-      console.log(chalk.green(url, response.statusCode))
-    } catch (error) {
-      console.log(chalk.red(url, error.response.statusCode))
-    }
-  }
-
-  Promise.all(apps.map(ping))
-}
diff --git a/script/remove-stale-staging-apps.js b/script/remove-stale-staging-apps.js
deleted file mode 100755
index 37be1c475f..0000000000
--- a/script/remove-stale-staging-apps.js
+++ /dev/null
@@ -1,145 +0,0 @@
-#!/usr/bin/env node
-
-// [start-readme]
-//
-// This script removes all stale Heroku staging apps that outlasted the closure
-// of their corresponding pull requests, or correspond to spammy pull requests.
-//
-// [end-readme]
-
-import dotenv from 'dotenv'
-import { chain } from 'lodash-es'
-import chalk from 'chalk'
-import Heroku from 'heroku-client'
-import getOctokit from './helpers/github.js'
-
-dotenv.config()
-
-// Check for required Heroku API token
-if (!process.env.HEROKU_API_TOKEN) {
-  console.error(
-    'Error! You must have a HEROKU_API_TOKEN environment variable for deployer-level access.'
-  )
-  process.exit(1)
-}
-// Check for required GitHub PAT
-if (!process.env.GITHUB_TOKEN) {
-  console.error('Error! You must have a GITHUB_TOKEN environment variable for repo access.')
-  process.exit(1)
-}
-
-const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN })
-// This helper uses the `GITHUB_TOKEN` implicitly
-const octokit = getOctokit()
-
-const protectedAppNames = ['help-docs']
-
-main()
-
-async function main() {
-  const apps = chain(await heroku.get('/apps'))
-    .orderBy('name')
-    .value()
-
-  const prInfoMatch = /^(?:gha-|ghd-)?(?<repo>docs(?:-internal)?)-(?<pullNumber>\d+)--.*$/
-
-  const appsPlusPullIds = apps.map((app) => {
-    const match = prInfoMatch.exec(app.name)
-    const { repo, pullNumber } = (match || {}).groups || {}
-
-    return {
-      app,
-      repo,
-      pullNumber: parseInt(pullNumber, 10) || null,
-    }
-  })
-
-  const appsWithPullIds = appsPlusPullIds.filter((appi) => appi.repo && appi.pullNumber > 0)
-
-  const nonMatchingAppNames = appsPlusPullIds
-    .filter((appi) => !(appi.repo && appi.pullNumber > 0))
-    .map((appi) => appi.app.name)
-    .filter((name) => !protectedAppNames.includes(name))
-
-  let staleCount = 0
-  let spammyCount = 0
-  for (const awpi of appsWithPullIds) {
-    const { isStale, isSpammy } = await assessPullRequest(awpi.repo, awpi.pullNumber)
-
-    if (isSpammy) spammyCount++
-    if (isStale) staleCount++
-
-    if (isSpammy || isStale) {
-      await deleteHerokuApp(awpi.app.name)
-    }
-  }
-
-  const matchingCount = appsWithPullIds.length
-  const counts = {
-    total: matchingCount,
-    alive: matchingCount - staleCount,
-    stale: {
-      total: staleCount,
-      spammy: spammyCount,
-      closed: staleCount - spammyCount,
-    },
-  }
-  console.log(`🧮 COUNTS!\n${JSON.stringify(counts, null, 2)}`)
-
-  const nonMatchingCount = nonMatchingAppNames.length
-  if (nonMatchingCount > 0) {
-    console.log(
-      '⚠️  👀',
-      chalk.yellow(
-        `Non-matching app names (${nonMatchingCount}):\n - ${nonMatchingAppNames.join('\n - ')}`
-      )
-    )
-  }
-}
-
-function displayParams(params) {
-  const { owner, repo, pull_number: pullNumber } = params
-  return `${owner}/${repo}#${pullNumber}`
-}
-
-async function assessPullRequest(repo, pullNumber) {
-  const params = {
-    owner: 'github',
-    repo: repo,
-    pull_number: pullNumber,
-  }
-
-  let isStale = false
-  let isSpammy = false
-  try {
-    const { data: pullRequest } = await octokit.pulls.get(params)
-
-    if (pullRequest && pullRequest.state === 'closed') {
-      isStale = true
-      console.debug(chalk.green(`STALE: ${displayParams(params)} is closed`))
-    }
-  } catch (error) {
-    // Using a standard GitHub PAT, PRs from spammy users will respond as 404
-    if (error.status === 404) {
-      isStale = true
-      isSpammy = true
-      console.debug(chalk.yellow(`STALE: ${displayParams(params)} is spammy or deleted`))
-    } else {
-      console.debug(chalk.red(`ERROR: ${displayParams(params)} - ${error.message}`))
-    }
-  }
-
-  return { isStale, isSpammy }
-}
-
-async function deleteHerokuApp(appName) {
-  try {
-    await heroku.delete(`/apps/${appName}`)
-    console.log('✅', chalk.green(`Removed stale app "${appName}"`))
-  } catch (error) {
-    console.log(
-      '❌',
-      chalk.red(`ERROR: Failed to remove stale app "${appName}" - ${error.message}`)
-    )
-  }
-}
diff --git a/script/remove-stale-staging-envs.js b/script/remove-stale-staging-envs.js
deleted file mode 100755
index d10f4742fa..0000000000
--- a/script/remove-stale-staging-envs.js
+++ /dev/null
@@ -1,266 +0,0 @@
-#!/usr/bin/env node
-
-// [start-readme]
-//
-// This script removes all stale GitHub deployment environments that outlasted
-// the closure of their corresponding pull requests, or correspond to spammy
-// pull requests.
-//
-// [end-readme]
-
-import dotenv from 'dotenv'
-import chalk from 'chalk'
-import getOctokit from './helpers/github.js'
-
-dotenv.config()
-
-// Check for required GitHub PAT
-if (!process.env.GITHUB_TOKEN) {
-  console.error('Error! You must have a GITHUB_TOKEN environment variable for repo access.')
-  process.exit(1)
-}
-
-if (!process.env.ELEVATED_TOKEN) {
-  console.error(
-    'Error! You must have a ELEVATED_TOKEN environment variable for removing deployment environments.'
-  )
-  process.exit(1)
-}
-
-if (!process.env.REPO) {
-  console.error('Error! You must have a REPO environment variable.')
-  process.exit(1)
-}
-
-if (!process.env.RUN_ID) {
-  console.error('Error! You must have a RUN_ID environment variable.')
-  process.exit(1)
-}
-
-// This helper uses the `GITHUB_TOKEN` implicitly
-const octokit = getOctokit()
-
-const protectedEnvNames = ['production']
-const maxEnvironmentsToProcess = 50
-
-// How long must a PR be closed without being merged to be considered stale?
-const ONE_HOUR = 60 * 60 * 1000
-const prClosureStaleTime = 2 * ONE_HOUR
-
-main()
-
-async function main() {
-  const owner = 'github'
-  const [repoOwner, repo] = (process.env.REPO || '').split('/')
-
-  if (repoOwner !== owner) {
-    console.error(`Error! The repository owner must be "${owner}" but was "${repoOwner}".`)
-    process.exit(1)
-  }
-
-  const logUrl = `https://github.com/${owner}/${repo}/actions/runs/${process.env.RUN_ID}`
-
-  const prInfoMatch = /^(?:gha-|ghd-)?(?<repo>docs(?:-internal)?)-(?<pullNumber>\d+)--.*$/
-
-  let exceededLimit = false
-  let matchingCount = 0
-  let staleCount = 0
-  let spammyCount = 0
-  const nonMatchingEnvNames = []
-
-  for await (const response of octokit.paginate.iterator(octokit.repos.getAllEnvironments, {
-    owner,
-    repo,
-  })) {
-    const { data: environments } = response
-
-    const envsPlusPullIds = environments.map((env) => {
-      const match = prInfoMatch.exec(env.name)
-      const { repo: repoName, pullNumber } = (match || {}).groups || {}
-
-      return {
-        env,
-        repo: repoName,
-        pullNumber: parseInt(pullNumber, 10) || null,
-      }
-    })
-
-    const envsWithPullIds = envsPlusPullIds.filter(
-      (eppi) => eppi.repo === repo && eppi.pullNumber > 0
-    )
-    matchingCount += envsWithPullIds.length
-
-    nonMatchingEnvNames.push(
-      ...envsPlusPullIds
-        .filter((eppi) => !(eppi.repo && eppi.pullNumber > 0))
-        .map((eppi) => eppi.env.name)
-        .filter((name) => !protectedEnvNames.includes(name))
-    )
-
-    for (const ewpi of envsWithPullIds) {
-      const { isStale, isSpammy } = await assessPullRequest(ewpi.pullNumber)
-
-      if (isSpammy) spammyCount++
-      if (isStale) staleCount++
-
-      if (isSpammy || isStale) {
-        await deleteEnvironment(ewpi.env.name)
-      }
-
-      if (spammyCount + staleCount >= maxEnvironmentsToProcess) {
-        exceededLimit = true
-        break
-      }
-    }
-
-    if (exceededLimit) {
-      console.log(
-        '🛑',
-        chalk.bgRed(`STOP! Exceeded limit, halting after ${maxEnvironmentsToProcess}.`)
-      )
-      break
-    }
-  }
-
-  const counts = {
-    total: matchingCount,
-    alive: matchingCount - staleCount,
-    stale: {
-      total: staleCount,
-      spammy: spammyCount,
-      closed: staleCount - spammyCount,
-    },
-  }
-  console.log(`🧮 COUNTS!\n${JSON.stringify(counts, null, 2)}`)
-
-  const nonMatchingCount = nonMatchingEnvNames.length
-  if (nonMatchingCount > 0) {
-    console.log(
-      '⚠️  👀',
-      chalk.yellow(
-        `Non-matching env names (${nonMatchingCount}):\n - ${nonMatchingEnvNames.join('\n - ')}`
-      )
-    )
-  }
-
-  function displayParams(params) {
-    const { owner, repo, pull_number: pullNumber } = params
-    return `${owner}/${repo}#${pullNumber}`
-  }
-
-  async function assessPullRequest(pullNumber) {
-    const params = {
-      owner,
-      repo,
-      pull_number: pullNumber,
-    }
-
-    let isStale = false
-    let isSpammy = false
-    try {
-      const { data: pullRequest } = await octokit.pulls.get(params)
-
-      if (pullRequest && pullRequest.state === 'closed') {
-        const isMerged = pullRequest.merged === true
-        const closureAge = Date.now() - Date.parse(pullRequest.closed_at)
-        isStale = isMerged || closureAge >= prClosureStaleTime
-
-        if (isStale) {
-          console.debug(chalk.green(`STALE: ${displayParams(params)} is closed`))
-        } else {
-          console.debug(
-            chalk.blue(`NOT STALE: ${displayParams(params)} is closed but not yet stale`)
-          )
-        }
-      }
-    } catch (error) {
-      // Using a standard GitHub PAT, PRs from spammy users will respond as 404
-      if (error.status === 404) {
-        isStale = true
-        isSpammy = true
-        console.debug(chalk.yellow(`STALE: ${displayParams(params)} is spammy or deleted`))
-      } else {
-        console.debug(chalk.red(`ERROR: ${displayParams(params)} - ${error.message}`))
-      }
-    }
-
-    return { isStale, isSpammy }
-  }
-
-  async function deleteEnvironment(envName) {
-    try {
-      let deploymentCount = 0
-
-      // Get all of the Deployments to signal this environment's complete deactivation
-      for await (const response of octokit.paginate.iterator(octokit.repos.listDeployments, {
-        owner,
-        repo,
-
-        // In the GitHub API, there can only be one active deployment per environment.
-        // For our many staging apps, we must use the unique appName as the environment.
-        environment: envName,
-      })) {
-        const { data: deployments } = response
-
-        // Deactivate ALL of the deployments
-        for (const deployment of deployments) {
-          // Deactivate this Deployment with an 'inactive' DeploymentStatus
-          await octokit.repos.createDeploymentStatus({
-            owner,
-            repo,
-            deployment_id: deployment.id,
-            state: 'inactive',
-            description: 'The app was undeployed',
-            log_url: logUrl,
-            // The 'ant-man' preview is required for `state` values of 'inactive', as well as
-            // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters.
-            // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'.
-            mediaType: {
-              previews: ['ant-man', 'flash'],
-            },
-          })
-
-          // Delete this Deployment
-          await octokit.repos.deleteDeployment({
-            owner,
-            repo,
-            deployment_id: deployment.id,
-          })
-
-          deploymentCount++
-        }
-      }
-
-      // Delete this Environment
-      try {
-        await octokit.repos.deleteAnEnvironment({
-          // Must use a PAT with more elevated permissions than GITHUB_TOKEN can achieve!
-          headers: {
-            authorization: `token ${process.env.ELEVATED_TOKEN}`,
-          },
-          owner,
-          repo,
-          environment_name: envName,
-        })
-      } catch (error) {
-        if (error.status !== 404) {
-          throw error
-        }
-      }
-
-      console.log(
-        '✅',
-        chalk.green(
-          `Removed stale deployment environment "${envName}" (${deploymentCount} deployments)`
-        )
-      )
-    } catch (error) {
-      console.log(
-        '❌',
-        chalk.red(
-          `ERROR: Failed to remove stale deployment environment "${envName}" - ${error.message}`
-        )
-      )
-    }
-  }
-}
diff --git a/tests/rendering/events.js b/tests/rendering/events.js
index 524b20d9e7..d06ac27196 100644
--- a/tests/rendering/events.js
+++ b/tests/rendering/events.js
@@ -31,6 +31,8 @@ describe('POST /events', () => {
     delete process.env.HYDRO_SECRET
     delete process.env.HYDRO_ENDPOINT
     csrfToken = ''
+
+    nock.cleanAll()
   })
 
   async function checkEvent(data, code) {
diff --git a/tests/rendering/robots-txt.js b/tests/rendering/robots-txt.js
index d7319d663f..c7e3871e93 100644
--- a/tests/rendering/robots-txt.js
+++ b/tests/rendering/robots-txt.js
@@ -35,9 +35,9 @@ describe('robots.txt', () => {
       })
   })
 
-  it('disallows indexing of herokuapp.com domains', async () => {
+  it('disallows indexing of azurecontainer.io domains', async () => {
     const req = {
-      hostname: 'docs-internal-12345--my-branch.herokuapp.com',
+      hostname: 'docs-internal-preview-12345-asdfz.azurecontainer.io',
       path: '/robots.txt',
     }
     const res = new MockExpressResponse()
diff --git a/tests/rendering/static-assets.js b/tests/rendering/static-assets.js
index 187071e386..285c54336a 100644
--- a/tests/rendering/static-assets.js
+++ b/tests/rendering/static-assets.js
@@ -1,7 +1,8 @@
 import fs from 'fs'
 import path from 'path'
 
-import { expect } from '@jest/globals'
+import nock from 'nock'
+import { expect, jest } from '@jest/globals'
 
 import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js'
 import { get } from '../helpers/supertest.js'
@@ -69,3 +70,99 @@ describe('static assets', () => {
     checkCachingHeaders(res, true, 60)
   })
 })
+
+describe('archived enterprise static assets', () => {
+  // Sometimes static assets are proxied. The URL for the static asset
+  // might not indicate it's based on archived enterprise version.
+
+  jest.setTimeout(60 * 1000)
+
+  beforeAll(async () => {
+    // The first page load takes a long time so let's get it out of the way in
+    // advance to call out that problem specifically rather than misleadingly
+    // attributing it to the first test
+    // await get('/')
+
+    const sampleCSS = '/* nice CSS */'
+
+    nock('https://github.github.com')
+      .get('/help-docs-archived-enterprise-versions/2.21/_next/static/foo.css')
+      .reply(200, sampleCSS, {
+        'content-type': 'text/css',
+        'content-length': sampleCSS.length,
+      })
+    nock('https://github.github.com')
+      .get('/help-docs-archived-enterprise-versions/2.21/_next/static/only-on-proxy.css')
+      .reply(200, sampleCSS, {
+        'content-type': 'text/css',
+        'content-length': sampleCSS.length,
+      })
+    nock('https://github.github.com')
+      .get('/help-docs-archived-enterprise-versions/2.3/_next/static/only-on-2.3.css')
+      .reply(200, sampleCSS, {
+        'content-type': 'text/css',
+        'content-length': sampleCSS.length,
+      })
+    nock('https://github.github.com')
+      .get('/help-docs-archived-enterprise-versions/2.3/_next/static/fourofour.css')
+      .reply(404, 'Not found', {
+        'content-type': 'text/plain',
+      })
+    nock('https://github.github.com')
+      .get('/help-docs-archived-enterprise-versions/2.3/assets/images/site/logo.png')
+      .reply(404, 'Not found', {
+        'content-type': 'text/plain',
+      })
+  })
+
+  afterAll(() => nock.cleanAll())
+
+  it('should proxy if the static asset is prefixed', async () => {
+    const res = await get('/enterprise/2.21/_next/static/foo.css', {
+      headers: {
+        Referrer: '/enterprise/2.21',
+      },
+    })
+    expect(res.statusCode).toBe(200)
+    checkCachingHeaders(res, true, 60)
+  })
+  it('should proxy if the Referrer header indicates so', async () => {
+    const res = await get('/_next/static/only-on-proxy.css', {
+      headers: {
+        Referrer: '/enterprise/2.21',
+      },
+    })
+    expect(res.statusCode).toBe(200)
+    checkCachingHeaders(res, true, 60)
+  })
+  it('should proxy if the Referrer header indicates so', async () => {
+    const res = await get('/_next/static/only-on-2.3.css', {
+      headers: {
+        Referrer: '/en/enterprise-server@2.3/some/page',
+      },
+    })
+    expect(res.statusCode).toBe(200)
+    checkCachingHeaders(res, true, 60)
+  })
+  it('might still 404 even with the right referrer', async () => {
+    const res = await get('/_next/static/fourofour.css', {
+      headers: {
+        Referrer: '/en/enterprise-server@2.3/some/page',
+      },
+    })
+    expect(res.statusCode).toBe(404)
+    checkCachingHeaders(res, true, 60)
+  })
+
+  it('404 on the proxy but actually present here', async () => {
+    const res = await get('/assets/images/site/logo.png', {
+      headers: {
+        Referrer: '/en/enterprise-server@2.3/some/page',
+      },
+    })
+    // It tried to go via the proxy, but it wasn't there, but then it
+    // tried "our disk" and it's eventually there.
+    expect(res.statusCode).toBe(200)
+    checkCachingHeaders(res, true, 60)
+  })
+})
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index 664c43aab5..b66f6d180b 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -38,7 +38,7 @@ Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %},
 1. Solicita el nombre de usuario de la persona a la que estás invitando como colaborador.{% ifversion fpt or ghec %} Si aún no tiene un nombre de usuario, puede registrarse para {% data variables.product.prodname_dotcom %} Para obtener más información, consulta "[Registrar una cuenta {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account)".{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%}
 {% data reusables.repositories.click-collaborators-teams %}
 1. Da clic en **Invitar un colaborador**. ![botón de "invitar un colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png)
 2. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field-user.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 027c3629b8..9c9e625b8d 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -30,7 +30,7 @@ Aunque se borren las bifurcaciones de los repositorios privados cuando se elimin
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
 4. Da clic en {% octicon "trash" aria-label="The trash icon" %} a la derecha del colaborador que quieres eliminar. ![Botón para eliminar un colaborador](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 3be45c2a1b..4dfccdaf02 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -21,7 +21,7 @@ shortTitle: Eliminarte a ti mismo
 ---
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
 {% else %}
 2. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/settings-sidebar-repositories.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index d8335fc89f..5c314444e4 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -22,7 +22,7 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 
 {% note %}
 
-**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
+**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 36a4e1b60b..d2da20b22b 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -69,7 +69,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Build with Gradle
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: build
 ```
@@ -106,7 +106,7 @@ steps:
   - name: Validate Gradle wrapper
     uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
   - name: Run the Gradle package task
-    uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+    uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
     with:
       arguments: -b ci.gradle package
 ```
@@ -135,7 +135,7 @@ steps:
   - name: Validate Gradle wrapper
     uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
   - name: Build with Gradle
-    uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+    uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
     with:
       arguments: build
   - uses: actions/upload-artifact@v2
diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 6ca54788a1..3795a144fd 100644
--- a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -47,7 +47,7 @@ Si defines el `entrypoint` en un archivo de metadatos de una acción, este inval
 
 La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. Para obtener más información acerca de las formas _exec_ y _shell_, consulta la sección [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) en la documentación de Docker.
 
-You should not use `WORKDIR` to specify your entrypoint in your Dockerfile. Instead, you should use an absolute path. For more information, see [WORKDIR](#workdir).
+No deberías utilizar `WORKDIR` para especificar el punto de entrada en tu Dockerfile. En vez de esto, deberías utilizar una ruta absoluta. Para obtener más información, consulta la sección [WORKDIR](#workdir).
 
 Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`.
 
@@ -101,7 +101,7 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
 
 ### CMD
 
-If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
+Si defines el `args` en el archivo de metadatos de la acción, `args` invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
 
 Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos:
 
diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 2eaa836207..3427268d05 100644
--- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 4
 
 ## Acerca de la nueva sintaxis YAML para {% data variables.product.prodname_actions %}
 
-All actions require a metadata file. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
+Todas las acciones requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos en el archivo de metadatos definen las configuraciones de entradas, salidas y ejecuciones de tu acción.
 
 Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
@@ -41,7 +41,7 @@ Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAM
 
 **Opcional** Los parámetros de entrada te permiten especificar datos que la acción espera para usar durante el tiempo de ejecución. {% data variables.product.prodname_dotcom %} almacena parámetros de entrada como variables de entorno. Las Id de entrada con letras mayúsculas se convierten a minúsculas durante el tiempo de ejecución. Recomendamos usar Id de entrada en minúsculas.
 
-### Example: Specifying inputs
+### Ejemplo: Especificar las entradas
 
 Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with` (con), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)".
 
@@ -84,13 +84,13 @@ Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `oc
 
 **Opcional** Si se utiliza el parámetro de entrada, esta `string` se registrará como un mensaje de advertencia. Puedes utilizar esta advertencia para notificar a los usuarios que la entrada es obsoleta y mencionar cualquier alternativa.
 
-## `outputs` for Docker container and JavaScript actions
+## `outputs` para las acciones de contenedores de Docker y JavaScript
 
 **Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior.  Por ejemplo, si tuviste una acción que realizó la adición de dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada.
 
 Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)".
 
-### Example: Declaring outputs for Docker container and JavaScript actions
+### Ejemplo: Declarar las salidas para las acciones de contenedores de Docker y JavaScript
 
 ```yaml
 outputs:
@@ -108,9 +108,9 @@ outputs:
 
 ## `outputs` para las acciones compuestas
 
-**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
+Las `outputs` **opcionales** utilizan los mismos parámetros que `outputs.<output_id>` y `outputs.<output_id>.description` (consulta la sección de "[`outputs` para acciones de contenedores de Docker y JavaScript](#outputs-for-docker-container-and-javascript-actions)"), pero también incluye el token `value`.
 
-### Example: Declaring outputs for composite actions
+### Ejemplo: Declarar las salidas para las acciones compuestas
 
 {% raw %}
 ```yaml
@@ -135,13 +135,13 @@ Para obtener más información sobre cómo utilizar la sintaxis de contexto, con
 
 ## `runs`
 
-**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed.
+**Requerido** Especifica si es una acción de JavaScript, una acción compuesta o una acción de contenedor de Docker y cómo se ejecuta esta.
 
 ## `runs` para acciones de JavaScript
 
 **Requerido** Configura la ruta al código de la acción y el tiempo de ejecución que se utiliza para ejecutarlo.
 
-### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
+### Ejemplo: Utilizar Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
 ```yaml
 runs:
@@ -162,7 +162,7 @@ runs:
 
 ### `runs.pre`
 
-**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
+**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. La acción `pre` siempre se ejecuta predeterminadamente, pero puedes invalidar esto utilizando [`runs.pre-if`](#runspre-if).
 
 En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`:
 
@@ -365,11 +365,11 @@ runs:
 ```
 {% endif %}
 
-## `runs` for Docker container actions
+## `runs` para las acciones de contenedores de Docker
 
-**Required** Configures the image used for the Docker container action.
+**Requerido** Configura la imagen que se utiliza para la acción de contenedores de Docker.
 
-### Example: Using a Dockerfile in your repository
+### Ejemplo: Utilizar un Dockerfile en tu repositorio
 
 ```yaml
 runs:
@@ -377,7 +377,7 @@ runs:
   image: 'Dockerfile'
 ```
 
-### Example: Using public Docker registry container
+### Ejemplo: Utilizar un contenedor de registro público de Docker
 
 ```yaml
 runs:
@@ -391,7 +391,7 @@ runs:
 
 ### `runs.pre-entrypoint`
 
-**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
+**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `pre-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes anular esto utilizando [`runs.pre-if`](#runspre-if).
 
 El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo.
 
@@ -423,7 +423,7 @@ Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consu
 
 ### `post-entrypoint`
 
-**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
+**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `post-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes anular esto utilizando [`runs.post-if`](#runspost-if).
 
 ```yaml
 runs:
@@ -447,7 +447,7 @@ Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta eje
 
 Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)".
 
-#### Example: Defining arguments for the Docker container
+#### Ejemplo: Definir argumentos para el contenedor de Docker
 
 {% raw %}
 ```yaml
@@ -465,7 +465,7 @@ runs:
 
 Puedes usar un color y un icono de [Pluma](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-### Example: Configuring branding for an action
+### Ejemplo: Configurar la personalización de una acción
 
 ```yaml
 branding:
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index b1bd8075ff..52cc87e50c 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
 
 You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 1. Click **New self-hosted runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
@@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
 
 You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 1. Click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 
@@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use
 
 New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
 1. Click **Add new**, then click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
-{% ifversion ghec or ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
 
 {% data reusables.github-actions.self-hosted-runner-public-repo-access %}
-{% endif %}
 
 ### Making enterprise runners available to repositories
 
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index ebeb8d58da..12f78de075 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -46,7 +46,7 @@ Los ejecutores auto-hospedados se asignan automáticamente al grupo predetermina
 
 Cuando creas un grupo, debes elegir una política que defina qué repositorios tienen acceso al grupo ejecutor.
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
@@ -61,12 +61,11 @@ Cuando creas un grupo, debes elegir una política que defina qué repositorios t
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. En la sección de "Ejecutores auto-hospedados", haz clic en **Agregar nuevo** y luego en **Grupo nuevo**.
+1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**.
 
     ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group.png)
 1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio.
@@ -95,7 +94,7 @@ Los ejecutores auto-hospedados se asignan automáticamente al grupo predetermina
 
 Cuando creas un grupo, debes elegir la política que defina qué organizaciones tienen acceso al grupo de ejecutores.
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -113,8 +112,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -144,7 +142,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones
 ## Cambiar la política de acceso de un grupo de ejecutores auto-hospedados
 
 Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo.
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
 1. Modifica las opciones de acceso o cambia el nombre del grupo de ejecutores.
@@ -158,8 +156,7 @@ Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo.
    Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
 {% endif %}
 
@@ -181,17 +178,18 @@ Could not find any self-hosted runner group named "rg-runnergroup".
 ## Mover un ejecutor auto-hospedado a un grupo
 
 Si no especificas un grupo de ejecutores durante el proceso de registro, tus ejecutores auto-hospedados nuevos se asignarán automáticamente al grupo predeterminado y después se moverán a otro grupo.
-{% ifversion ghec or ghes > 3.1 or ghae %}
+
 {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 1. En la lista de "Ejecutores", haz clic en aquél que quieras configurar.
 2. Selecciona el menú desplegable del grupo de ejecutores.
 3. En "Mover el ejecutor al grupo", elige un grupo destino para el ejecutor.
-{% endif %}
-{% ifversion ghes < 3.2 or ghae %}
-1. En la sección de "Ejecutores auto-hospedados" de la página de configuración, ubica el grupo actual del ejecutor que quieres mover y expande la lista de miembros del grupo. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png)
+{% elsif ghae or ghes < 3.4 %}
+1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png)
 2. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move.png)
 3. Para mover el ejecutor, da clic en el grupo de destino. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
+
 ## Eliminar un grupo de ejecutores auto-hospedados
 
 Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina.
@@ -201,8 +199,7 @@ Los ejecutores auto-hospedados se devuelven automáticamente al grupo predetermi
 1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
 2. Para eliminar el grupo, da clic en **Eliminar grupo**.
 3. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
-{% endif %}
-{% ifversion ghes < 3.2 or ghae %}
+{% elsif ghes < 3.2 %}
 1. En la sección de "Ejecutores auto-hospedados" de la página de ajustes, ubica el grupo que quieras borrar y haz clic en el botón {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
 1. Para eliminar el grupo, da clic en **Eliminar grupo**. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-remove.png)
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index 60cdee66e1..aad261e14c 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -30,20 +30,20 @@ shortTitle: Elimina ejecutores auto-hospedados
 Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)".
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
+
 ## Eliminar el ejecutor de una organización
 
 {% note %}
@@ -57,19 +57,20 @@ Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el
 Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)".
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+{% ifversion fpt or ghes > 3.3 or ghec %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% else %}
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
+
 ## Eliminar un ejecutor de una empresa
 
 {% ifversion fpt %}
@@ -85,19 +86,17 @@ Si utilizas
 
 {% endnote %}
 
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+To remove a self-hosted runner from an enterprise, you must be an enterprise owner. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
-{% ifversion ghec %}
-Para eliminar a un ejecutor auot-hospedado de una cuenta empresarial, debes ser un propietario de la empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo agregar un ejecutor auto-hospedado con la API de REST, consulta las [API de GitHub Actions para la Administración Empresarial](/rest/reference/enterprise-admin#github-actions).
+{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% elsif ghae or ghes %}
-Para eliminar un ejecutor auto-hospedado a nivel empresarial de
-{% data variables.product.product_location %}, debes ser un propietario de empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado.
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index b1e805297d..e3b4ce03b5 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -19,13 +19,13 @@ Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
 ## Crear una etiqueta personalizada
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
  1. En la sección de "Etiquetas", haz clic en {% octicon "gear" aria-label="The Gear icon" %}.
  1. En el campo de "Encuentra o crea una etiqueta", teclea el nombre de tu etiqueta nueva y haz clic en **Crear etiqueta nueva**. La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
@@ -34,35 +34,38 @@ Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a
 
 La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
+
 ## Asignar una etiqueta a un ejecutor auto-hospedado
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.runner-label-settings %}
   1. Para asignar una etiqueta a tu ejecutor auto-hospedado, en el campo de "Encuentra o crea una etiqueta", haz clic en ella.
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
 1. Da clic en la etiqueta para asignarla a tu ejecutor auto-hospedado.
 {% endif %}
+
 ## Eliminar una etiqueta personalizada de un ejecutor auto-hospedado
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.runner-label-settings %}
   1. En el campo "Encuentra o crea una etiqueta", las etiquetas asignadas se marcan con el
 icono {% octicon "check" aria-label="The Check icon" %}. Haz clic en una etiqueta marcada para desasignarla de tu ejecutor auto-hospedado.
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
 1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
+
 ## Utilizar el script de configuración para crear y asignar etiquetas
 
 Puedes utilizar el script de configuración en el ejecutor auto-hospedado para crear y asignar etiquetas personalizadas. Por ejemplo, este comando asigna una etiqueta llamada `gpu` al ejecutor auto-hospedado.
diff --git a/translations/es-ES/content/actions/learn-github-actions/expressions.md b/translations/es-ES/content/actions/learn-github-actions/expressions.md
index 091664c3ff..dc9f053988 100644
--- a/translations/es-ES/content/actions/learn-github-actions/expressions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md
@@ -50,12 +50,12 @@ env:
 
 Como parte de una expresión, puedes usar tipos de datos `boolean`, `null`, `number` o `string`.
 
-| Tipo de datos | Valor literal                                                                                                                                                                                                                 |
-| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `boolean`     | `verdadero` o `falso`                                                                                                                                                                                                         |
-| `null`        | `null`                                                                                                                                                                                                                        |
-| `number`      | Cualquier formato de número compatible con JSON.                                                                                                                                                                              |
-| `secuencia`   | You don't need to enclose strings in {% raw %}${{{% endraw %} and {% raw %}}}{% endraw %}. However, if you do, you must use single quotes around the string and escape literal single quotes with an additional single quote. |
+| Tipo de datos | Valor literal                                                                                                                                                                                                                                                                                                                         |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `boolean`     | `verdadero` o `falso`                                                                                                                                                                                                                                                                                                                 |
+| `null`        | `null`                                                                                                                                                                                                                                                                                                                                |
+| `number`      | Cualquier formato de número compatible con JSON.                                                                                                                                                                                                                                                                                      |
+| `secuencia`   | You don't need to enclose strings in `{% raw %}${{{% endraw %}` and `{% raw %}}}{% endraw %}`. However, if you do, you must use single quotes (`'`) around the string. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. |
 
 #### Ejemplo
 
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index 12d581031b..c1397f7825 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -96,7 +96,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env:
@@ -167,7 +167,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env:
@@ -246,7 +246,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env: {% raw %}
diff --git a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
index b86900fd20..8394d835de 100644
--- a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
@@ -85,8 +85,8 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | actions       | read/write  | none | read |
 | checks        | read/write  | none | read |
 | contents      | read/write  | read | read |
-| deployments   | read/write  | none | read |
-| id-token      | read/write  | none | read |
+| deployments   | read/write  | none | read |{% ifversion fpt or ghec %}
+| id-token      | read/write  | none | read |{% endif %}
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
index 80516f0aec..b9f7499abf 100644
--- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -202,6 +202,10 @@ El mismo principio que se describió anteriormente para utilizar acciones de ter
 {% data reusables.actions.outside-collaborators-internal-actions %} Para obtener más información, consulta la sección "[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)".
 {% endif %}
 
+## Using OpenSSF Scorecards to secure workflows
+
+[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions.
+
 ## Impacto potencial de un ejecutor puesto en riesgo
 
 Estas secciones consideran algunos de los pasos que puede llevar a cabo un atacante si pueden ejecutar comandos malintencionados en un ejecutor de {% data variables.product.prodname_actions %}.
diff --git a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md
index 92fad1018d..4425732fab 100644
--- a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -917,8 +917,6 @@ on:
 ```yaml
 on:
   push:
-    types:
-      - opened
     branches:    
       - 'releases/**'
     paths:
@@ -960,8 +958,6 @@ on:
 ```yaml
 on:
   push:
-    types:
-      - opened
     branches:    
       - 'releases/**'
     paths:
@@ -996,9 +992,9 @@ on:
 
 ### `lanzamiento`
 
-| Carga del evento Webhook                                                                       | Tipos de actividad                                                                                                                                              | `GITHUB_SHA`                                     | `GITHUB_REF`            |
-| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------- |
-| [`lanzamiento`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Última confirmación en el lanzamiento etiquetado | Etiqueta de lanzamiento |
+| Carga del evento Webhook                                                                       | Tipos de actividad                                                                                                                                              | `GITHUB_SHA`                                     | `GITHUB_REF`                                    |
+| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------- |
+| [`lanzamiento`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Última confirmación en el lanzamiento etiquetado | Tag ref of release `refs/tags/<tag_name>` |
 
 {% note %}
 
diff --git a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 788f2c0eda..cae52e535d 100644
--- a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -314,7 +314,9 @@ Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos tempor
 
 {% warning %}
 
-**Advertencia:** en Windows, el PowerShell tradicional (`shell: powershell`) no utiliza el cifrado UTF-8 predeterminado. Asegúrate que escribes los archivos utilizando la codificación correcta. Por ejemplo, necesitas configurar la codificación UTF-8 cuando configuras la ruta:
+**Advertencia:** en Windows, el PowerShell tradicional (`shell: powershell`) no utiliza el cifrado UTF-8 predeterminado.
+
+When using `shell: powershell`, you must specify UTF-8 encoding. Por ejemplo:
 
 ```yaml
 jobs:
@@ -325,22 +327,7 @@ jobs:
         run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
 ```
 
-O cambia a PowerShell Core, el cual tiene predeterminado el UTF-8:
-
-```yaml
-jobs:
-  modern-pwsh-example:
-    uses: windows-2019
-    steps:
-      - shell: pwsh
-        run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8
-```
-
-Puedes obtener más detalles sobre el UTF-8 y PowerShell Core en esta genial [respuesta de Stack Overflow](https://stackoverflow.com/a/40098904/162694):
-
-> ### Lectura opcional: La perspectiva multiplataforma: PowerShell _Core_:
-> 
-> [PowerShell ahora es multiplataforma](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/)a través de su edición **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)**, cuyo cifrado ***se predetermina sensiblemente em ***BOM-less UTF-8****** en línea con las plataformas similares a las de Unix.
+Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8.
 
 {% endwarning %}
 
diff --git a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 2d62328779..f3c3379e0b 100644
--- a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -830,7 +830,7 @@ services:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
-      password: ${{ secrets.ghcr_token }}
+      password: ${{ secrets.github_token }}
   myservice2:
     image: dockerhub_org/myservice2
     credentials:
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 61e750cc30..6afb61b812 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -699,7 +699,7 @@ All Storage tests passed
 
 `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}.
 
-For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/).
+For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/).
 
 ### git-import-detect
 
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
index 81a40ba9f7..31a26cb6ef 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
@@ -34,7 +34,7 @@ High Availability (HA) and Clustering both provide redundancy by eliminating the
 
 ## Backups and disaster recovery
 
-Neither HA or Clustering should be considered a replacement for regular backups. For more information, see "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)."
+Neither HA nor Clustering should be considered a replacement for regular backups. For more information, see "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)."
 
 ## Monitoring
 
diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 0a28fc6e08..13fc45c5ab 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -47,7 +47,7 @@ Probamos y damos compatibilidad oficial de los siguientes IdP. Para el SSO de SA
 | -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
 | Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
 | Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
-| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | OneLogin                                     | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | PingOne                                      | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | Shibboleth                                   | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index 4b55fc72f2..d36d729ba3 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,7 +18,7 @@ shortTitle: Llaves de implementación
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
 {% else %}
 3. En la barra lateral izquierda, haz clic en **Deploy keys** (Llaves de implementación). ![Parámetro de llaves de implementación](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index fd74f77479..d71f381530 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -22,7 +22,7 @@ shortTitle: Registro de seguridad
 La bitácora de seguridad lista todas las acciones que se llevaron a cabo en los últimos 90 días.
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else %}
 1. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. ![Pestaña de registro de seguridad](/assets/images/help/settings/audit-log-tab.png)
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index df9cf5e4e1..8c0f496ee8 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -24,7 +24,7 @@ shortTitle: Actualizar las credenciales de acceso
 1. Para solicitar una contraseña nueva, visita {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
 2. Ingresa la dirección de correo electrónico asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y luego haz clic en **Enviar correo electrónico para restablecer contraseña.** El correo electrónico se enviará a la dirección de respaldo en caso de que la hayas configurado. ![Diálogo de solicitud de correo electrónico de restablecimiento de contraseña](/assets/images/help/settings/password-recovery-email-request.png)
 3. Te enviaremos por correo electrónico un enlace que te permitirá restablecer la contraseña. Debes hacer clic en este enlace dentro de las 3 horas posteriores a haber recibido el correo electrónico. Si no recibiste un correo electrónico de nuestra parte, asegúrate de revisar la carpeta de spam.
-4. Si habilitaste la autenticación bifactorial, se te pedirán tus credenciales de 2FA. Teclea tus credenciales bifactoriales o uno de tus códigos de recuperación de 2FA y haz clic en **Verificar**. ![Mensaje de autenticación bifactorial](/assets/images/help/2fa/2fa-password-reset.png)
+4. Si habilitaste la autenticación bifactorial, se te pedirán tus credenciales de 2FA. Type your authentication code or one of your recovery codes and click **Verify**. If you have added a security key to your account, you can insert the key and click **Use security key** instead of typing an authentication code. ![Mensaje de autenticación bifactorial](/assets/images/help/2fa/2fa-password-reset.png)
 5. Teclea una contraseña nueva, confírmala y haz clic en **Cambiar contraseña**. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)."
   {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
   ![Casilla de recuperación de contraseña](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index da0a24aa20..afa9fa9f67 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -20,7 +20,10 @@ shortTitle: Recuperar una cuenta con 2FA
 
 {% warning %}
 
-**Advertencia**: {% data reusables.two_fa.support-may-not-help %}
+**Advertencias**:
+
+- {% data reusables.two_fa.support-may-not-help %}
+- {% data reusables.accounts.you-must-know-your-password %}
 
 {% endwarning %}
 
@@ -28,12 +31,21 @@ shortTitle: Recuperar una cuenta con 2FA
 
 ## Utilizar un código de recuperación de autenticación de dos factores
 
-Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
 
-{% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
-2. Da clic en **Ingresar un código de recuperación de dos factores** debajo de "¿Tienes Problemas?". ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
-2. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**. ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
-3. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**. ![Campo para escribir un código de recuperación y botón Verificar](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+{% data reusables.two_fa.username-password %}
+
+{% ifversion fpt or ghec %}
+1. Under "Having problems?", click **Use a recovery code or request a reset**.
+
+   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png)
+{%- else %}
+1. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**.
+
+   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+1. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**.
+
+   ![Campo para escribir un código de recuperación y botón Verificar](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
 
 {% ifversion fpt or ghec %}
 ## Autenticar con un número de reserva
@@ -43,38 +55,52 @@ Si pierdes el acceso a tu app TOTP principal o número de teléfono, puedes prop
 
 ## Autenticar con una clave de seguridad
 
-Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
+Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
 
 {% ifversion fpt or ghec %}
 ## Autentificarse con un dispositivo verificado, token SSH, o token de acceso personal
 
-Si conoces tu contraseña de {% data variables.product.product_name %} pero no tienes credenciales o códigos de autenticación bifactorial, se te puede enviar una contraseña de única ocasión a tu dirección de correo electrónico verificada para comenzar con el proceso de verificación y volver a obtener acceso a tu cuenta.
+If you know your password for {% data variables.product.product_location %} but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
 
 {% note %}
 
-**Nota**: Por razones de seguridad, recobrar el acceso a tu cuenta autenticándose con una contraseña de una sola ocasión puede demorar de 3 a 5 días hábiles. Las solicitudes adicionales emitidas durante este periodo no se revisarán.
+**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time.
 
 {% endnote %}
 
 Puedes utilizar tus credenciales de autenticación de dos factores para recobrar el acceso a tu cuenta en cualquier momento durante el periodo de espera de 3 a 5 días.
 
-1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación. Si no conoces tu contraseña de {% data variables.product.product_name %}, no podrás generar una contraseña de una sola ocasión.
-2. Da clic en **¿No puedes acceder a tu dispositivo de dos factores o a tus códigos de recuperación válidos?** debajo de "¿Tienes Problemas ![Enlace si no tienes tu dispositivo de 2fa o códigos de recuperación](/assets/images/help/2fa/no-access-link.png)
-3. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación. ![Botón de restablecimiento de configuración de autenticación](/assets/images/help/2fa/reset-auth-settings.png)
-4. Da clic en **Enviar contraseña de una sola vez** para enviarla a todas las direcciones de correo electrónico asociadas con tu cuenta. ![Botón para enviar contraseña de una sola vez](/assets/images/help/2fa/send-one-time-password.png)
-5. Debajo de "Contraseña de una sola vez", teclea la contraseña temporal del correo electrónico de recuperación que envió {% data variables.product.prodname_dotcom %}. ![Campo para contraseña de una sola vez](/assets/images/help/2fa/one-time-password-field.png)
-6. Da clic en **Verificar dirección de correo electrónico**.
-7. Escoge un factor de verificación alterno.
+1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación.
+
+    {% warning %}
+
+    **Advertencia**: {% data reusables.accounts.you-must-know-your-password %}
+
+    {% endwarning %}
+1. Under "Having problems?", click **Use a recovery code or request a reset**.
+
+   ![Screenshot of link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
+1. To the right of "Locked out?", click **Try recovering your account**.
+
+   ![Screenshot of link to try recovering your account](/assets/images/help/2fa/try-recovering-your-account-link.png)
+1. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación.
+
+    ![Screenshot of button to start reset of authentication settings](/assets/images/help/2fa/reset-auth-settings.png)
+1. Click **Send one-time password** to send a one-time password to all eligible addresses associated with your account. Only verified emails are eligible for account recovery. If you've restricted password resets to your primary and/or backup addresses, these addresses are the only addresses eligible for account recovery.
+
+   ![Screenshot of button to send one-time password](/assets/images/help/2fa/send-one-time-password.png)
+1. Debajo de "Contraseña de una sola vez", teclea la contraseña temporal del correo electrónico de recuperación que envió {% data variables.product.prodname_dotcom %}.
+
+   ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png)
+1. Da clic en **Verificar dirección de correo electrónico**.
+
+   ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png)
+1. Escoge un factor de verificación alterno.
     - Si utilizaste tu dispositivo actual para ingresar en esta cuenta anteriormente y te gustaría utilizarlo para verificación, haz clic en **Verificar con este dispositivo**.
     - Si has configurado una llave SSH previamente en esta cuenta y quieres utilizarla para verificación, da clic en **Llave SSH**.
-    - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**. ![Botones de verificación alternativa](/assets/images/help/2fa/alt-verifications.png)
-8. Un miembro de {% data variables.contact.github_support %} revisará tu solicitud y te enviará un mensaje de correo electrónico dentro de los siguientes 3 a 5 días. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional.
+    - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**.
+
+   ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png)
+1. A member of {% data variables.contact.github_support %} will review your request and email you within three business days. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional.
 
 {% endif %}
-
-## Leer más
-
-- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)"
-- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)"
-- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)"
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index aad0d4625e..5a6a77e511 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -76,7 +76,7 @@ Al final de cada mes, {% data variables.product.prodname_dotcom %} calcula el co
 
 ### Ejemplo de cálculos de costo por minuto
 
-Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %} y permite gastos ilimitados, utilizar 15,000 minutos podría tener un costo extra de almacenamiento y minutos de $56 USD dependiendo de los sistemas operativos que se utilizan para ejecutar jobs.
+Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %} y permite gastos ilimitados, utilizar 5,000 minutos podría tener un costo extra de almacenamiento y minutos de $56 USD dependiendo de los sistemas operativos que se utilizan para ejecutar jobs.
 
 - 5,000 minutos (3,000 de Linux y 2,000 de Windows) = $56 USD ($24 USD + $32 USD).
   - 3,000 minutos de Linux a $0.008 USD por minuto = $24 USD.
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index 6bc71eec09..4193fb6b34 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -54,10 +54,12 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el
 {% data reusables.codespaces.exporting-changes %}
 ## Administrar las notificaciones de uso y límite de gastos
 
-Las notificaciones por correo electrónico se envían a los propietarios de las cuentas y gerentes de facturación cuando el límite de gastos llega a 50%, 75%, y 90% del límite de gastos de tu cuenta.
+Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
 
 Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**.
 
+![Screenshot of the billing email notification settings](/assets/images/help/billing/codespaces-spending-limit-notifications.png)
+
 ## Leer más
 
 - "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md
index 646ed3ccd5..b4db279d0b 100644
--- a/translations/es-ES/content/code-security/getting-started/github-security-features.md
+++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md
@@ -25,7 +25,7 @@ The {% data variables.product.prodname_advisory_database %} contains a curated l
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ### Security policy
-  
+
 Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
 {% endif %}
 
@@ -74,7 +74,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi
 
 ### {% data variables.product.prodname_secret_scanning_caps %}
 
-Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %} 
+Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %}
 {%- ifversion ghec or ghes or ghae %}
 {% ifversion ghec %}For private repositories, you can view {% elsif ghes or ghae %}View {% endif %}any secrets that {% data variables.product.company_short %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised.{% endif %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
 
@@ -84,6 +84,12 @@ Automatically detect tokens or credentials that have been checked into a reposit
 Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
 {% endif %}
 
+{% ifversion ghec or ghes > 3.1 %}
+### Security overview
+
+Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+{% endif %}
+
 ## Further reading
 - "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
 - "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
index 25412c70df..d27d4e08ce 100644
--- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
@@ -36,7 +36,7 @@ You can create a default security policy that will display in any of your organi
 {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %}
 ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
 
-{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
 
 1. Click your profile photo, then click **Organizations**.
 2. Click **Settings** next to your organization.
diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 947533b214..6e7ae7a841 100644
--- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -67,7 +67,14 @@ Before defining a custom pattern, you must ensure that {% data variables.product
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
-{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}
+1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**.
+1. When the dry run finishes, you'll see a sample of results (up to 1000) from the repository. Review the results and identify any false positive results.
+   ![Screenshot showing results from dry run](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. Edit the new custom pattern to fix any problems with the results, then click **Save and dry run** to test your changes.
+{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
+{% endif %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
@@ -116,6 +123,7 @@ Before defining a custom pattern, you must ensure that you enable {% data variab
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
@@ -139,6 +147,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 {% data reusables.enterprise-accounts.advanced-security-security-features %}
 1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index a4c299c3dd..9b97e577a9 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -30,11 +30,17 @@ shortTitle: Use Dependabot with Actions
 
 {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
 
-For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply:
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %}
+For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply:
+{% endif %}
 
 - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %}
 - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %}
+For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available.
+{% endif %}
+
 For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 8b835ed644..9a41ccbd2a 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -58,7 +58,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
 
 You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
index 6d2de3a534..f0e5dc57aa 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
@@ -46,8 +46,6 @@ There are three reasons why an alert may have no pull request link:
 
 If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert.
 
-![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png)
-
 ## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %}
 
 When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab.
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 2e0ad140d1..4a967cf2fb 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -103,17 +103,17 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the
 {% ifversion fpt or ghec %}
 ## Does each dependency vulnerability generate a separate alert?
 
-When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability.
+When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest.
 
-The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities.
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png)
 
-![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png)
+Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest.
 
-When you click to display the alert details, you can see how many vulnerabilities are included in the alert.
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png)
 
-![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
+The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies.
 
-**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers.
+**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
 {% endif %}
 
 ## Further reading
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index c2a6b0c128..4029faa7f6 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -25,7 +25,7 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
@@ -37,11 +37,30 @@ You can enable automatic security updates for any repository that uses {% data v
 ## About updates for vulnerable dependencies in your repository
 
 {% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`).
+
+Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %}
 {% endif %}
 
 ## Viewing and updating vulnerable dependencies
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by.
+  ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png)
+1. Click the alert that you would like to view.
+  ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png)
+1. Review the details of the vulnerability and, if available, the pull request containing the automated security update.
+1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**.
+  ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
+1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
+1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert.
+   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png)
+
+{% elsif ghes = 3.3 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -54,7 +73,7 @@ You can enable automatic security updates for any repository that uses {% data v
 1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert.
    ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
-{% elsif ghes > 3.0 or ghae-issue-4864 %}
+{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 9dfc90486b..0956aede41 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -88,7 +88,7 @@ The recommended formats explicitly define which versions are used for all direct
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
 | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
 | Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
-{%- ifversion fpt or ghes > 3.3 %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %}
 | Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
 | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
 | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
index e34257a9bd..4cd476335b 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -21,6 +21,8 @@ Puedes reportar a los usuarios que hayan violado las condiciones de servicio o l
 
 Si se ha habilitado la capacidad para reportar contenido en un repositorio público, también puedes reportarlo directamente a los mantenedores del mismo.
 
+Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer).
+
 ## Informar un usuario
 
 {% data reusables.profile.user_profile_page_navigation %}
diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index 2d6b79b8a3..1bfa020663 100644
--- a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -293,10 +293,10 @@ El parámetro `redirect_uri` es opcional. Si se deja fuera, GitHub redireccionar
 
 El parámetro opcional `redirect_uri` también puede utilizarse para las URL de localhost. Si la aplicación especifica una URL y puerto de localhost, entonces, después de autorizar la aplicación, los usuarios se redireccionarán al puerto y URL proporcionados. La `redirect_uri` no necesita empatar con el puerto especificado en la url de rellamado para la app.
 
-Para la URL de rellamado de `http://localhost/path`, puedes utilizar esta `redirect_uri`:
+For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`:
 
 ```
-http://localhost:1234/path
+http://127.0.0.1:1234/path
 ```
 
 ## Crear tokens múltiples para Apps de OAuth
diff --git a/translations/es-ES/content/developers/overview/managing-deploy-keys.md b/translations/es-ES/content/developers/overview/managing-deploy-keys.md
index a0c48a6bdd..6a10d1d0c6 100644
--- a/translations/es-ES/content/developers/overview/managing-deploy-keys.md
+++ b/translations/es-ES/content/developers/overview/managing-deploy-keys.md
@@ -34,11 +34,11 @@ En muchos casos, especialmente al inicio de un proyecto, el reenvío del agente
 #### Configuración
 
 1. Habilita el reenvío de agente localmente. Consulta [nuestra guía sobre el redireccionamiento del agente SSH][ssh-agent-forwarding] para obtener más información.
-2. Configura tus scripts de despliegue para utilizar el reenvío de agente. For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh`
+2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, en un script de bash, el habilitar el reenvío de agentes se verá más o menos así: `ssh -A serverA 'bash -s' < deploy.sh`
 
 ## Clonado de HTTPS con tokens de OAuth
 
-If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
+Si no quieres utilizar llaves SSH, puedes utilizar HTTPS con tokens de OAuth.
 
 #### Pros
 
@@ -57,7 +57,7 @@ If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
 
 #### Configuración
 
-See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+Consulta [nuestra guía para crear tokens de acceso personal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
 
 ## Llaves de implementación
 
@@ -78,7 +78,7 @@ See [our guide on creating a personal access token](/authentication/keeping-your
 
 #### Configuración
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair key pair.
+1. [Ejecuta el procedimiento `ssh-keygen`][generating-ssh-keys] en tu servidor y recuerda dónde guardaste l par de llaves pública y privada de RSA generado.
 2. En la esquina superior derecha de cualquier página de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego da clic en **Tu perfil**. ![Navegación al perfil](/assets/images/profile-page.png)
 3. En tu página de perfil, da clic en **Repositorios** y luego en el nombre de tu repositorio. ![Enlace de los repositorios](/assets/images/repos.png)
 4. Desde tu repositorio, da clic en **Configuración**. ![Configuración del repositorio](/assets/images/repo-settings.png)
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index cd5871557a..2b722e32b8 100644
--- a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -46,10 +46,10 @@ Puedes integrar tu cuenta organizacional o personal en {% data variables.product
 
 ### Integración con Slack y con {% data variables.product.product_name %}
 
-Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, confirmaciones, lanzamientos, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Slack.
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. También puedes llevar a cabo actividades como cerrar o abrir propuestas y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Slack.
 
 The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace.
 
 ### Microsoft Teams y su integración con {% data variables.product.product_name %}
 
-Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambios, confirmaciones, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas, comentar en tus propuestas o solicitudes de cambios y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource.
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. También puedes llevar a cabo actividades como cerrar o abrir propuestas, comentar en tus propuestas o solicitudes de cambios y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource.
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 22af3c0bee..f41b494f8a 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -195,6 +195,8 @@ Utiliza el comando `git remote rm` para eliminar una URL remota de tu repositori
 El comando `git remote rm` toma un argumento:
 * El nombre de un remoto, por ejemplo `destination` (destino)
 
+Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.
+
 ## Ejemplo
 
 Estos ejemplos asumen que estás[clonando con HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), lo cual se recomienda.
@@ -217,7 +219,7 @@ $ git remote -v
 
 {% warning %}
 
-**Nota**: `git remote rm` no elimina el repositorio remoto del servidor.  Simplemente, elimina de tu repositorio local el remoto y sus referencias.
+**Note**: `git remote rm` does not delete the remote repository from the server.  Simplemente, elimina de tu repositorio local el remoto y sus referencias.
 
 {% endwarning %}
 
diff --git a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md
index 7f19a514f0..9d2a6a3c80 100644
--- a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -37,10 +37,29 @@ Una licencia de {% data variables.product.prodname_GH_advanced_security %} propo
 - **Resumen de seguridad** - Revisa la configuración de seguridad y las alertas para una organización e identifica los repositorios que tienen un riesgo mayor. Para obtener más información, consulta la sección "[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)".
 {% endif %}
 
+{% ifversion fpt or ghec %}
+The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. |{% ifversion fpt %}
+|                          |          Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %}
+|:------------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:|
+|    Escaneo de código     |                  Sí                  |                                          No                                          |                                        Sí                                         |
+|   Escaneo de secretos    | Yes **(limited functionality only)** |                                          No                                          |                                        Sí                                         |
+| Revisión de dependencias |                  Sí                  |                                          No                                          |                                        Sí                                         |{% endif %}
+|
+{% ifversion ghec %}
+|                          |          Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %}
+|:------------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:|
+|    Escaneo de código     |                  Sí                  |                                          No                                          |                                        Sí                                         |
+|   Escaneo de secretos    | Yes **(limited functionality only)** |                                          No                                          |                                        Sí                                         |
+| Revisión de dependencias |                  Sí                  |                                          No                                          |                                        Sí                                         |
+|   Resumen de seguridad   |                  No                  |                                          No                                          |                                        Sí                                         |
+{% endif %}
+
+{% endif %}
+
 Para obtener más información sobre las características de {% data variables.product.prodname_advanced_security %} que se encuentran en desarrollo, consulta la sección "[Plan de trabajo de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para obtener un resumen de todas las características de seguridad, consulta la sección "[Características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
 {% ifversion fpt or ghec %}
-Las características de la {% data variables.product.prodname_GH_advanced_security %} se encuentran habilitadas para todos los repositorios públicos de {% data variables.product.prodname_dotcom_the_website %}. Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %} pueden habilitar estas características adicionalmente para repositorios privados e internos. También tienen acceso a un resumen de seguridad a nivel organizacional. {% ifversion fpt %}Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %} pueden habilitar estas características adicionalmente para repositorios privados e internos. They also have access to an organization-level security overview. {% ifversion fpt %}Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
 {% endif %}
 
 {% ifversion ghes or ghec %}
diff --git a/translations/es-ES/content/github/site-policy/github-community-guidelines.md b/translations/es-ES/content/github/site-policy/github-community-guidelines.md
index ca8f4e0b39..0b69762ebc 100644
--- a/translations/es-ES/content/github/site-policy/github-community-guidelines.md
+++ b/translations/es-ES/content/github/site-policy/github-community-guidelines.md
@@ -22,7 +22,7 @@ El propósito principal de la comunidad de GitHub es colaborar en proyectos de s
 
 * **Se cordial y de mentalidad abierta** - Otros colaboradores pueden no tener el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para aportar. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar.
 
-* **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones.
+* **Respect each other** - Nothing sabotages healthy conversation like rudeness. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones.
 
   Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación.
 
diff --git a/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md b/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md
index c82741151b..2a4f9e4f65 100644
--- a/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md
+++ b/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md
@@ -23,3 +23,5 @@ La Política de Marcas de GitHub se puede utilizar para informar del contenido q
 
 ## [Política de Eliminación de Información Privada de GitHub](/github/site-policy/github-private-information-removal-policy)
 La Política de Eliminación de Información Privada de GitHub puede utilizarse para reportar datos que sean privados (confidenciales y que posean un riesgo de seguridad), pero que no se protege necesariamente por derechos de autor o comerciales.
+
+Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer).
diff --git a/translations/es-ES/content/graphql/overview/about-the-graphql-api.md b/translations/es-ES/content/graphql/overview/about-the-graphql-api.md
index 0219a1d363..c3e47bffc1 100644
--- a/translations/es-ES/content/graphql/overview/about-the-graphql-api.md
+++ b/translations/es-ES/content/graphql/overview/about-the-graphql-api.md
@@ -12,7 +12,7 @@ topics:
 
 ## Resumen
 
-Aquí hay algunos enlaces rápidos para ponerte en marcha con la API de GraphQL v4:
+Here are some quick links to get you up and running with the GraphQL API:
 
 * [Autenticación](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)
 * [Terminal raíz](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint)
@@ -36,9 +36,9 @@ El lenguaje de consulta de [GraphQL](https://graphql.github.io/) es:
 
 ## Por qué GitHub utiliza GraphQL
 
-GitHub eligió GraphQL para la API v4 porque ofrece significativamente más flexibilidad para nuestros intregradores. La capacidad de definir precisamente los datos que quieres &mdash;y _únicamente_ estos&mdash; es una ventaja poderosa sobre las terminales de la API de REST v3. GraphQL te permite reemplazar varias solicitudes de REST con _una sola llamada_ para agregar los datos que especifiques.
+GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want&mdash;and _only_ the data you want&mdash;is a powerful advantage over traditional REST API endpoints. GraphQL te permite reemplazar varias solicitudes de REST con _una sola llamada_ para agregar los datos que especifiques.
 
-Para obtener más detalles acerca de por qué GitHub se ha migrado a GraphQL, consulta la[publicación de anuncios del blog](https://githubengineering.com/the-github-graphql-api/).
+For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/).
 
 ## Acerca de la referencia del modelo de GraphQL
 
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
index 9b7a3176c5..09ced50e76 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -19,9 +19,9 @@ shortTitle: Revisar las integraciones instaladas
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
-{% elsif ghae or ghes < 3.4 %}
+{% else %}
 1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %} Instaladas**. ![Pestaña de {% data variables.product.prodname_github_apps %} instaladas en la barra lateral de parámetros de la organización](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 {% endif %}
 2. Al lado de la {% data variables.product.prodname_github_app %} que quieras revisar, haz clic en **Configure** (Configurar). ![Botón Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png)
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index 172b741d51..e08fcb498f 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -40,7 +40,7 @@ To further support your team's collaboration abilities, you can upgrade to {% da
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index a2e83c9e8c..0912210e99 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -28,9 +28,9 @@ Cuando eliminas a un colaborador de un repositorio en tu organización, el colab
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
 {% data reusables.organizations.invite-teams-or-people %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index 2daf35b81f..830749095f 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -24,7 +24,7 @@ Cuando inhabilitas los tableros de proyecto, ya no ves la información de los ta
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
 {% endif %}
 1. Decide si deseas inhabilitar los tableros de proyecto que se usan en toda la organización, los tableros de proyecto de los repositorios de la organización, o ambos. Luego, en "Proyectos":
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
index f17db4ef13..30bfbd3d25 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -10,12 +10,12 @@ versions:
 shortTitle: Integrar Jira
 ---
 
-{% ifversion ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. ![Pestaña de aplicaciones OAuth de la barra lateral izquierda](/assets/images/help/organizations/org-oauth-applications-ghe.png)
 1. Da clic en **Nueva App de OAuth**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 {% data reusables.user_settings.access_settings %}
 1. En la barra lateral izquierda en **Organization settings** (Configuraciones de la organización), haz clic en el nombre de tu organización. ![Barra lateral Organization name (Nombre de la organización)](/assets/images/help/settings/organization-settings-from-sidebar.png)
 1. En la barra lateral de **Developer settings** (Configuraciones del programador), haz clic en **OAuth applications** (Aplicaciones OAuth). ![Pestaña de aplicaciones OAuth de la barra lateral izquierda](/assets/images/help/organizations/org-oauth-applications-ghe.png)
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index a6fab36ae1..b7b22e5688 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -15,11 +15,15 @@ topics:
 shortTitle: Restringir la creación de repositorios
 ---
 
-Puedes elegir si los miembros pueden crear repositorios en tu organización o no. Si permites que los miembros creen repositorios, puedes elegir qué tipos de repositorios pueden crear.{% ifversion fpt or ghec %} Para permitir que los miembros creen solo repositorios privados, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} Para obtener más información, consulta la sección "[Acerca de los repositorios](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" en la documentación de {% data variables.product.prodname_ghe_cloud %}{% endif %}.
+Puedes elegir si los miembros pueden crear repositorios en tu organización o no. {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository.
+
+{% ifversion fpt %}
+Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization).
+{% endif %}
 
-Los propietarios de la organización siempre pueden crear cualquier tipo de repositorio.
 {% ifversion ghec or ghae or ghes %}
-{% ifversion ghec or ghae %}Los propietarios de empresas{% elsif ghes %}Los administradores de sitio{% endif %} pueden restringir las opciones que tienes disponibles para la política de creación de repositorios de tu organización. {% ifversion ghec or ghes or ghae %} Para obtener más información, consulta la sección "[Restringir la creación de repositorios en tu empresa.](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% endif %}{% endif %}
+Enterprise owners can restrict the options you have available for your organization's repository creation policy. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)".
+{% endif %}
 
 {% warning %}
 
@@ -36,5 +40,12 @@ Los propietarios de la organización siempre pueden crear cualquier tipo de repo
    ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
    ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+
+   {% note %}
+
+   **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.
+
+   {% endnote %}
    {%- endif %}
+
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 8cb00329e2..4e14267508 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -57,7 +57,7 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. In the left sidebar, click **Code review**
@@ -73,7 +73,7 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. In the left sidebar, click **Code review**
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index 1408b3e897..fb1dedf12d 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -21,7 +21,7 @@ topics:
 
 **Note:** When working with pull requests, keep the following in mind:
 * If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes.
-* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
+* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index f9a5eda3a6..6a9ee0d344 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -16,7 +16,7 @@ topics:
 ---
 Forking a repository is similar to copying a repository, with two major differences:
 
-* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository.
+* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository.
 * You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository.
 
 {% data reusables.repositories.you-can-fork %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
index 79122863a5..7cd3d1e498 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -22,7 +22,7 @@ Si usas Zendesk para hacer el seguimiento de los tickets informados por el usuar
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
 {% else %}
 1. En la barra lateral izquierda, haz clic en **Autolink references** (Referencias de enlace automático). ![Pestaña Autolink references (Referencias de enlace automático) en la barra lateral izquierda](/assets/images/help/repository/autolink-references-tab.png)
diff --git a/translations/es-ES/content/rest/reference/billing.md b/translations/es-ES/content/rest/reference/billing.md
index 8876b25d3f..fe0cf42be4 100644
--- a/translations/es-ES/content/rest/reference/billing.md
+++ b/translations/es-ES/content/rest/reference/billing.md
@@ -4,6 +4,7 @@ intro: 'With the Billing API, you can monitor the charges and usage {% data vari
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '>=3.4'
 topics:
   - API
 miniTocMaxHeadingLevel: 3
diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md
index d903396303..230e3f76b5 100644
--- a/translations/es-ES/content/rest/reference/enterprise-admin.md
+++ b/translations/es-ES/content/rest/reference/enterprise-admin.md
@@ -68,7 +68,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer
 
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5528 %}
 
 ## Audit log
 
@@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer
 
 {% endif %}
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 %}
 ## Billing
 
 {% for operation in currentRestOperations %}
diff --git a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md
index 3a5a6c13cc..7e8bf148cb 100644
--- a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md
@@ -921,6 +921,9 @@ _Equipos_
 {% ifversion fpt or ghes > 3.0 or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (:read)
 {% endif -%}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5435 -%}
+- [`GET /orgs/:org/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (:read)
+{% endif -%}
 
 {% ifversion fpt or ghes or ghec %}
 ### Permiso sobre los "ejecutores auto-hospedados"
diff --git a/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md b/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md
new file mode 100644
index 0000000000..f4795c3909
--- /dev/null
+++ b/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md
@@ -0,0 +1 @@
+If you protect your personal account with two-factor authentication but do not know your password, you will not be able to generate a one-time password to recover your account. {% data variables.product.company_short %} can send a password reset email to a verified address associated with your account. For more information, see "[Updating your {% data variables.product.prodname_dotcom %} access credentials](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)."
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
index d697ff8f8c..d645231024 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
@@ -8,6 +8,6 @@ container:
   image: ghcr.io/owner/image
   credentials:
      username: ${{ github.actor }}
-     password: ${{ secrets.ghcr_token }}
+     password: ${{ secrets.github_token }}
 ```
 {% endraw %}
diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
index 8669a6386e..9fd6e9c891 100644
--- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
+++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
@@ -2,6 +2,8 @@
    1. Debes proporcionar por lo menos el nombre de tu patrón y una expresión regular para el formato de tu patrón secreto.
    1. Puedes hacer clic en **{% octicon "chevron-down" aria-label="down" %} Más opciones** para proporcionar otro tipo de contenido circundante o requisitos de coincidencia adicionales para el formato de secreto.
    1. Proporciona una secuencia de pruebas de muestra para asegurarte de que tu configuración empate con los patrones que esperas.
-
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}
    ![Crear un formato de patrón personalizado del {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/secret-scanning-create-custom-pattern.png)
-1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}.
+   {% else %}
+   ![Crear un formato de patrón personalizado del {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png)
+   {% endif %}
diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
new file mode 100644
index 0000000000..8f4453f9fc
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
@@ -0,0 +1 @@
+1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern**{% elsif  ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}.
diff --git a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index 3570a95f99..b657745630 100644
--- a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else  %}
 1. En la barra lateral de Parámetros, haz clic en **Audit Log (Registro de auditoría)**. ![Parámetros de registro de auditoría de org en barra lateral](/assets/images/help/organizations/org-settings-audit-log.png)
diff --git a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index 5fa3e3d89e..a765d398be 100644
--- a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 3. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else  %}
 3. En la barra lateral izquierda, haz clic en **Audit Log (Registro de auditoría)**. ![Pestaña de registro de auditoría](/assets/images/enterprise/site-admin-settings/audit-log-tab.png)
diff --git a/translations/es-ES/data/reusables/billing/email-notifications.md b/translations/es-ES/data/reusables/billing/email-notifications.md
index d63f90e91c..9ab590e394 100644
--- a/translations/es-ES/data/reusables/billing/email-notifications.md
+++ b/translations/es-ES/data/reusables/billing/email-notifications.md
@@ -1,3 +1,5 @@
-Las notificaciones por correo electrónico se envían a los propietarios de cuenta y gerentes de facturación cuando los gastos llegan a 50%, 75%, y 90% del uso incluido en tu cuenta y cuando llegan a 50%, 75%, y 90% del límite de gastos de la misma.
+Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
 
 Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**.
+
+![Screenshot of the billing email notification settings](/assets/images/help/billing/actions-packages-spending-limit-notifications.png)
diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md b/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md
index 622983c8bc..ea5f3fdc9f 100644
--- a/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md
+++ b/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
-{% elsif ghes > 3.2%}
+{% else %}
 1. En la barra lateral, haz clic en **{% data variables.product.prodname_dependabot %}**. ![Opción de la barra lateral de secretos del {% data variables.product.prodname_dependabot %}](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
index 8c23fd1fdb..313c4302de 100644
--- a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
@@ -5,8 +5,8 @@ permissions:
   actions: read|write|none
   checks: read|write|none
   contents: read|write|none
-  deployments: read|write|none
-  id-token: read|write|none
+  deployments: read|write|none{% ifversion fpt or ghec %}
+  id-token: read|write|none{% endif %}
   issues: read|write|none
   discussions: read|write|none
   packages: read|write|none
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
index 711516a636..984c076d12 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
@@ -12,6 +12,6 @@
      2. En la barra lateral izquierda, da clic en **Resumen empresarial**.
      3. En la barra lateral de la empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Políticas**.{% endif %}
 2. Navega a los ajustes de los "Grupos de ejecutores":
-   * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec %} y luego en **Grupos de ejecutores** debajo de ella{% endif %}.{% ifversion ghec or ghes or ghae %}
-   * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion ghec %}, y luego en la pestaña de **Grupos de ejecutores** {% endif %}.{% endif %}
+   * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %}
+   * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %}
 {% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/sidebar-secret.md b/translations/es-ES/data/reusables/github-actions/sidebar-secret.md
index a2074b1dd5..0c5a37b1e5 100644
--- a/translations/es-ES/data/reusables/github-actions/sidebar-secret.md
+++ b/translations/es-ES/data/reusables/github-actions/sidebar-secret.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral izquierda, haz clic en **Secrets** (Secretos).
 {% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/billing_plans.md b/translations/es-ES/data/reusables/organizations/billing_plans.md
index 4debbde75b..60b7acac48 100644
--- a/translations/es-ES/data/reusables/organizations/billing_plans.md
+++ b/translations/es-ES/data/reusables/organizations/billing_plans.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral de configuración de tu organización, haz clic en **Planes & facturación**. ![Configuración de facturación](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md
index f897834b74..982008d449 100644
--- a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md
+++ b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %}**. ![Ajustes de las {% data variables.product.prodname_github_apps %}](/assets/images/help/organizations/github-apps-settings-sidebar.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/member-privileges.md b/translations/es-ES/data/reusables/organizations/member-privileges.md
index bf781907c4..19bfc3fae5 100644
--- a/translations/es-ES/data/reusables/organizations/member-privileges.md
+++ b/translations/es-ES/data/reusables/organizations/member-privileges.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
-{% elsif ghae or ghes < 3.4 %}
+{% else %}
 4. En la barra lateral izquierda, da clic en **Privilegios de los miembros**. ![Opción de privilegios de los miembros en la configuración de la organización](/assets/images/help/organizations/org-settings-member-privileges.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/repository-defaults.md b/translations/es-ES/data/reusables/organizations/repository-defaults.md
index b94201e0c1..4353dc97f8 100644
--- a/translations/es-ES/data/reusables/organizations/repository-defaults.md
+++ b/translations/es-ES/data/reusables/organizations/repository-defaults.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral izquierda da clic en **Predeterminados del repositorio**. ![Pestaña de predeterminados del repositorio](/assets/images/help/organizations/repo-defaults-tab.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/security-and-analysis.md b/translations/es-ES/data/reusables/organizations/security-and-analysis.md
index 3a4f474484..6cfb829475 100644
--- a/translations/es-ES/data/reusables/organizations/security-and-analysis.md
+++ b/translations/es-ES/data/reusables/organizations/security-and-analysis.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Pestaña de "Seguridad & análisis"](/assets/images/help/organizations/org-settings-security-and-analysis.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/security.md b/translations/es-ES/data/reusables/organizations/security.md
index cbd048958c..c0e89bec63 100644
--- a/translations/es-ES/data/reusables/organizations/security.md
+++ b/translations/es-ES/data/reusables/organizations/security.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
 {% else  %}
 1. En la barra lateral izquierda, da clic en **Seguridad de la organización**.
diff --git a/translations/es-ES/data/reusables/organizations/teams_sidebar.md b/translations/es-ES/data/reusables/organizations/teams_sidebar.md
index 082f84c9a5..59d119121d 100644
--- a/translations/es-ES/data/reusables/organizations/teams_sidebar.md
+++ b/translations/es-ES/data/reusables/organizations/teams_sidebar.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
 {% else %}
 1. En la barra lateral de Configuración, da clic en **Equipos**. ![Pestaña de equipos en la barra lateral de configuración de la organización](/assets/images/help/settings/settings-sidebar-team-settings.png)
diff --git a/translations/es-ES/data/reusables/organizations/verified-domains.md b/translations/es-ES/data/reusables/organizations/verified-domains.md
index 7702d9adbc..8a89d9f17c 100644
--- a/translations/es-ES/data/reusables/organizations/verified-domains.md
+++ b/translations/es-ES/data/reusables/organizations/verified-domains.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral izquierda, haz clic en **Dominios verificados & aprobados**. ![pestaña de "dominios aprobados & verificados"](/assets/images/help/organizations/verified-domains-button.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/pages/sidebar-pages.md b/translations/es-ES/data/reusables/pages/sidebar-pages.md
index 5744bf07f6..98cf17070e 100644
--- a/translations/es-ES/data/reusables/pages/sidebar-pages.md
+++ b/translations/es-ES/data/reusables/pages/sidebar-pages.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %}
+{% ifversion fpt or ghes > 3.4 or ghec or ghae-issue-5658 %}
 1. In the "Code & operations" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% else %}
 1. En la barra lateral izquierda, da clic en **Páginas**. ![Pestaña de página en la barra lateral izquierda](/assets/images/help/pages/pages-tab.png)
diff --git a/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md
index 3dac684983..13dd07c7a0 100644
--- a/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -1,4 +1,4 @@
-Puedes programar un flujo de trabajo para que se ejecute en horarios UTC específicos usando [sintaxis de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Los flujos de trabajo programados se ejecutan en la confirmación más reciente en la rama base o en la rama por defecto. El intervalo más corto en el que puedes programar flujos de trabajo es cada 15 minutos.
+Puedes programar un flujo de trabajo para que se ejecute en horarios UTC específicos usando [sintaxis de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Los flujos de trabajo programados se ejecutan en la confirmación más reciente en la rama base o en la rama por defecto. El intervalo más corto en el que puedes programar flujos de trabajo es cada 5 minutos.
 
 Este ejemplo activa el flujo de trabajo diariamente a las 5:30 y 17:30 UTC:
 
diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md
index 692a3dfcbe..d8fe749521 100644
--- a/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md
+++ b/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![pestaña de "Seguridad & análisis" en la configuración de repositorio](/assets/images/help/repository/security-and-analysis-tab.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/repositories/repository-branches.md b/translations/es-ES/data/reusables/repositories/repository-branches.md
index 3d0f401d22..8d0c4d1ece 100644
--- a/translations/es-ES/data/reusables/repositories/repository-branches.md
+++ b/translations/es-ES/data/reusables/repositories/repository-branches.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. En el menú izquierdo, da clic en **Ramas**. ![Sub-menú de opciones de repositorio](/assets/images/help/repository/repository-options-branch.png)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md
index eb6745e85c..93a4ef9a2c 100644
--- a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
 {% else %}
 1. Da clic en **Notificaciones**. ![Botón de notificaciones en la barra lateral](/assets/images/help/settings/notifications_menu.png)
diff --git a/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md b/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md
new file mode 100644
index 0000000000..2d3121b0cd
--- /dev/null
+++ b/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md
@@ -0,0 +1,6 @@
+
+{% note %}
+
+**Note:** The dry run feature is currently in beta and subject to change.
+
+{% endnote %}
diff --git a/translations/es-ES/data/reusables/user_settings/access_applications.md b/translations/es-ES/data/reusables/user_settings/access_applications.md
index 2fe392350c..766d040d6c 100644
--- a/translations/es-ES/data/reusables/user_settings/access_applications.md
+++ b/translations/es-ES/data/reusables/user_settings/access_applications.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
 {% else %}
 1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). ![Pestaña de aplicaciones](/assets/images/help/settings/settings-applications.png)
diff --git a/translations/es-ES/data/reusables/user_settings/account_settings.md b/translations/es-ES/data/reusables/user_settings/account_settings.md
index 6adb2aee80..bd0c4ea2bc 100644
--- a/translations/es-ES/data/reusables/user_settings/account_settings.md
+++ b/translations/es-ES/data/reusables/user_settings/account_settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-next %}
 1. En la barra lateral izquierda, haz clic en **{% octicon "gear" aria-label="The gear icon" %} Account** (Cuenta).
 {% else %}
 1. En la barra lateral izquierda, da clic en **Cuenta**. ![Opción de menú de configuración de cuenta](/assets/images/help/settings/settings-sidebar-account-settings.png)
diff --git a/translations/es-ES/data/reusables/user_settings/appearance-settings.md b/translations/es-ES/data/reusables/user_settings/appearance-settings.md
index 5b3fb50d32..ef71e7c1e9 100644
--- a/translations/es-ES/data/reusables/user_settings/appearance-settings.md
+++ b/translations/es-ES/data/reusables/user_settings/appearance-settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 {% else %}
 1. En la barra lateral de configuración de usuario, da clic en **Apariencia**.
diff --git a/translations/es-ES/data/reusables/user_settings/developer_settings.md b/translations/es-ES/data/reusables/user_settings/developer_settings.md
index 2313297a74..ba2bf33f9f 100644
--- a/translations/es-ES/data/reusables/user_settings/developer_settings.md
+++ b/translations/es-ES/data/reusables/user_settings/developer_settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
 {% else %}
 1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Configuración de desarrollador](/assets/images/help/settings/developer-settings.png)
diff --git a/translations/es-ES/data/reusables/user_settings/emails.md b/translations/es-ES/data/reusables/user_settings/emails.md
index 4701b9b984..88122b4e3b 100644
--- a/translations/es-ES/data/reusables/user_settings/emails.md
+++ b/translations/es-ES/data/reusables/user_settings/emails.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
 {% else %}
 1. En la barra lateral izquierda, da clic en **Correos Electrónicos**. ![Pestaña de correos electrónicos](/assets/images/help/settings/settings-sidebar-emails.png)
diff --git a/translations/es-ES/data/reusables/user_settings/organizations.md b/translations/es-ES/data/reusables/user_settings/organizations.md
index 0a19839a55..adb1d43dc5 100644
--- a/translations/es-ES/data/reusables/user_settings/organizations.md
+++ b/translations/es-ES/data/reusables/user_settings/organizations.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% else %}
 1. En la barra lateral de configuración de usuario, da clic en **Organizaciones**. ![Configuración de usuario para organizaciones](/assets/images/help/settings/settings-user-orgs.png)
diff --git a/translations/es-ES/data/reusables/user_settings/repo-tab.md b/translations/es-ES/data/reusables/user_settings/repo-tab.md
index 07a8e9af62..f4567a37a5 100644
--- a/translations/es-ES/data/reusables/user_settings/repo-tab.md
+++ b/translations/es-ES/data/reusables/user_settings/repo-tab.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
 {% else %}
 1. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/repos-tab.png)
diff --git a/translations/es-ES/data/reusables/user_settings/saved_replies.md b/translations/es-ES/data/reusables/user_settings/saved_replies.md
index b47b23628e..ef142883b7 100644
--- a/translations/es-ES/data/reusables/user_settings/saved_replies.md
+++ b/translations/es-ES/data/reusables/user_settings/saved_replies.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
 {% else %}
 1. En la barra lateral izquierda, da clic en **Respuestas guardadas**. ![Pestaña de respuestas guardadas](/assets/images/help/settings/saved-replies-tab.png)
diff --git a/translations/es-ES/data/reusables/user_settings/security-analysis.md b/translations/es-ES/data/reusables/user_settings/security-analysis.md
index c54b43346e..73dd008738 100644
--- a/translations/es-ES/data/reusables/user_settings/security-analysis.md
+++ b/translations/es-ES/data/reusables/user_settings/security-analysis.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
 {% else %}
 1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Configuración de análisis y seguridad](/assets/images/help/settings/settings-sidebar-security-analysis.png)
diff --git a/translations/es-ES/data/reusables/user_settings/security.md b/translations/es-ES/data/reusables/user_settings/security.md
index ef37e871ec..93faa88e31 100644
--- a/translations/es-ES/data/reusables/user_settings/security.md
+++ b/translations/es-ES/data/reusables/user_settings/security.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
 {% else %}
 1. En la barra lateral izquierda, da clic en **Seguridad de cuenta**. ![Configuración de seguridad para la cuenta del usuario](/assets/images/help/settings/settings-sidebar-account-security.png)
diff --git a/translations/es-ES/data/reusables/user_settings/ssh.md b/translations/es-ES/data/reusables/user_settings/ssh.md
index 44d51f35ff..da561daf8d 100644
--- a/translations/es-ES/data/reusables/user_settings/ssh.md
+++ b/translations/es-ES/data/reusables/user_settings/ssh.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
 {% else %}
 1. En la barra lateral de configuración de usuario, da clic en **Llaves SSH y GPG**. ![Llaves de autenticación](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
index b86900fd20..8394d835de 100644
--- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
@@ -85,8 +85,8 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | actions       | read/write  | none | read |
 | checks        | read/write  | none | read |
 | contents      | read/write  | read | read |
-| deployments   | read/write  | none | read |
-| id-token      | read/write  | none | read |
+| deployments   | read/write  | none | read |{% ifversion fpt or ghec %}
+| id-token      | read/write  | none | read |{% endif %}
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 61e750cc30..6afb61b812 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -699,7 +699,7 @@ All Storage tests passed
 
 `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}.
 
-For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/).
+For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/).
 
 ### git-import-detect
 
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 70e03b1efa..cca33717f5 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -64,7 +64,7 @@ If you know your password for {% data variables.product.product_location %} but
 
 {% note %}
 
-**注釈**: セキュリティ上の理由から、ワンタイムパスワードで認証してアカウントへのアクセスを回復するには、1〜3 営業日かかる場合があります。 {% data variables.product.company_short %} will not review additional requests submitted during this time.
+**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time.
 
 {% endnote %}
 
@@ -101,6 +101,6 @@ If you know your password for {% data variables.product.product_location %} but
     - If you've previously set up a personal access token and would like to use the personal access token for verification, click **Personal access token**.
 
    ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png)
-1. {% data variables.contact.github_support %}のメンバーがリクエストをレビューし、1〜3 営業日以内にメールでお知らせします。 リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。
+1. A member of {% data variables.contact.github_support %} will review your request and email you within three business days. リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。
 
 {% endif %}
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index a8cc636585..cd495e0341 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -76,7 +76,7 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e
 
 ### Sample minutes cost calculation
 
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
 
 - 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
   - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
diff --git a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
index 89bcf4cde1..74c583d24e 100644
--- a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
+++ b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -21,6 +21,8 @@ You can report users that have violated {% data variables.product.prodname_dotco
 
 If reported content is enabled for a public repository, you can also report content directly to repository maintainers.
 
+Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer).
+
 ## Reporting a user
 
 {% data reusables.profile.user_profile_page_navigation %}
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md
index f90be1a859..6be7725c53 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -195,6 +195,8 @@ Use the `git remote rm` command to remove a remote URL from your repository.
 `git remote rm` コマンドは 1 つの引数を取ります:
 * リモート名 (`destination` など)
 
+Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.
+
 ## サンプル
 
 次の例は (推奨されるとおり) [HTTPS を使用してクローンを作成](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)したと想定しています。
@@ -217,7 +219,7 @@ $ git remote -v
 
 {% warning %}
 
-**メモ**: `git remote rm` はリモートリポジトリをサーバから削除するわけではありません。  リモートとその参照をローカルリポジトリから削除するだけです。
+**Note**: `git remote rm` does not delete the remote repository from the server.  リモートとその参照をローカルリポジトリから削除するだけです。
 
 {% endwarning %}
 
diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md
index c8b27e59df..0231b06a5a 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -36,10 +36,31 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th
 - **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
 {% endif %}
 
+{% ifversion fpt or ghec %}
+The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories.
+
+{% ifversion fpt %}
+|                   | Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} |
+| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: |
+| Code scanning     | Yes                         | No                                           | Yes                                        |
+| Secret scanning   | Yes **(limited functionality only)** | No                                           | Yes                                       |
+| Dependency review | Yes                         | No                                           | Yes                                       |
+{% endif %}
+{% ifversion ghec %}
+|                   | Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} |
+| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: |
+| Code scanning     | Yes                         | No                                           | Yes                                        |
+| Secret scanning   | Yes **(limited functionality only)** | No                                           | Yes                                       |
+| Dependency review | Yes                         | No                                           | Yes                                       |
+| Security overview | No                          | No                                           | Yes                                          |
+{% endif %}
+
+{% endif %}
+
 For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
 {% ifversion fpt or ghec %}
-{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
 {% endif %}
 
 {% ifversion ghes or ghec %}
@@ -59,9 +80,9 @@ The site administrator must enable {% data variables.product.prodname_advanced_s
 Once your system is set up, you can enable and disable these features at the organization or repository level.
 
 {%- elsif ghec %}
-For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. 
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
 
-For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. 
+For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level.
 
 {%- elsif ghae %}
 You can enable and disable these features at the organization or repository level.
diff --git a/translations/ja-JP/content/github/site-policy/github-community-guidelines.md b/translations/ja-JP/content/github/site-policy/github-community-guidelines.md
index ef578e91c1..6989bc5a0e 100644
--- a/translations/ja-JP/content/github/site-policy/github-community-guidelines.md
+++ b/translations/ja-JP/content/github/site-policy/github-community-guidelines.md
@@ -22,7 +22,7 @@ GitHub コミュニティの主な目的は、ソフトウェアプロジェク
 
 * **広い心で受け入れる** - 他のコラボレータとあなたとでは、経験値やバックグラウンドが異なるかもしれませんが、だからといって相手がコントリビューションにつながる良いアイデアを持っていないということにはなりません。 新たなコラボレータや、かけだしのユーザーは歓迎してあげましょう。
 
-* **お互いを尊重し合うこと。**無礼な態度ほど、健全な会話を妨げるものはありません。 礼儀正しく、大人の態度を保ちましょう。一般的に攻撃的、虐待的、ヘイトスピーチとみなされるような内容を投稿しないでください。 嫌がらせや、人が悲しむような行為は禁止されています。 あらゆるやり取りにおいて、お互いに品位と配慮をもって接しましょう。
+* **Respect each other** - Nothing sabotages healthy conversation like rudeness. 礼儀正しく、大人の態度を保ちましょう。一般的に攻撃的、虐待的、ヘイトスピーチとみなされるような内容を投稿しないでください。 嫌がらせや、人が悲しむような行為は禁止されています。 あらゆるやり取りにおいて、お互いに品位と配慮をもって接しましょう。
 
   意見に反対したいこともあるでしょう。 それは全くかまいません。 ただし、批判すべきはアイデアであって、人ではありません。 悪口、個人攻撃、投稿の内容ではなく口調に対する応答、脊髄反射的な反論を行うのではなく、 会話の質を高めるような、理論的な反論を行いましょう。
 
diff --git a/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md b/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md
index a473a51ce0..e5d9e5cf14 100644
--- a/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md
+++ b/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md
@@ -23,3 +23,5 @@ GitHub トレードマークポリシーは、ブランドまたはビジネス
 
 ## [GitHub個人情報削除ポリシー](/github/site-policy/github-private-information-removal-policy)
 GitHub個人情報削除ポリシーは、個人的 (機密性が高く、セキュリティリスクをもたらす) で、著作権または商標によって保護されていないデータの報告に使用できます。
+
+Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer).
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 31fc46c1a1..0c6c4064ee 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -59,21 +59,21 @@ Pull Requestの説明またはコミットメッセージで、サポートさ
 
 {% ifversion fpt or ghes or ghae or ghec %}手動でリンクを解除できるのは、手動でリンクされたPull Requestだけです。 キーワードを使用してリンクしたIssueのリンクを解除するには、Pull Requestの説明を編集してそのキーワードを削除する必要があります。{% endif %}
 
-クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むプルリクエストは、リンクされたプルリクエストとしてリストされません。
+クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むPull Requestは、リンクされたPull Requestとしてリストされません。
 
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## 手動でプルリクエストをIssueにリンクする
+## 手動でPull RequestをIssueにリンクする
 
-リポジトリへの書き込み権限があるユーザなら誰でも、手動でプルリクエストをIssueにリンクできます。
+リポジトリへの書き込み権限があるユーザなら誰でも、手動でPull RequestをIssueにリンクできます。
 
-手動で1つのプルリクエストごとに最大10個のIssueをリンクできます。 Issueとプルリクエストは同じリポジトリになければなりません。
+手動で1つのPull Requestごとに最大10個のIssueをリンクできます。 IssueとPull Requestは同じリポジトリになければなりません。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-3. プルリクエストのリストで、Issueにリンクしたいプルリクエストをクリックします。
+3. Pull Requestのリストで、IssueにリンクしたいPull Requestをクリックします。
 4. 右のサイドバーで、[**Linked issues**] をクリックします。 ![右サイドバーの [Linked issues]](/assets/images/help/pull_requests/linked-issues.png)
-5. プルリクエストにリンクするIssueをクリックします。 ![Issueをリンクするドロップダウン](/assets/images/help/pull_requests/link-issue-drop-down.png)
+5. Pull RequestにリンクするIssueをクリックします。 ![Issueをリンクするドロップダウン](/assets/images/help/pull_requests/link-issue-drop-down.png)
 {% endif %}
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md
index d7f2c04d44..9ee10df6d4 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md
@@ -20,7 +20,7 @@ topics:
 
 ## 必要な環境
 
-Issueを作成するにはリポジトリが必要です。 書き込みアクセス権を持つ既存のリポジトリを利用することも、新しいリポジトリを作成することもできます。 {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 リポジトリでIssueが無効化されている場合、Issueを有効化する方法に関する情報については「[Issueの無効化](/github/administering-a-repository/managing-repository-settings/disabling-issues)」を参照してください。
+Issueを作成するにはリポジトリが必要です。 書き込みアクセス権を持つ既存のリポジトリを利用することも、新しいリポジトリを作成することもできます。 {% data reusables.enterprise-accounts.emu-permission-repo %} リポジトリはIssueを有効化していなければなりません。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 リポジトリでIssueが無効化されている場合、Issueを有効化する方法に関する情報については「[Issueの無効化](/github/administering-a-repository/managing-repository-settings/disabling-issues)」を参照してください。
 
 ## 空のIssueのオープン
 
@@ -81,7 +81,7 @@ Issueを既存のプロジェクトに追加できます。 {% ifversion fpt or
 
 ## コミュニケーション
 
-Issueを作成した後は、そのIssueにコメントを追加して会話を続けてください。 コラボレータあるいはTeamを@メンションして、コメントに注意を惹きつけることができます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 くわしいじょうほうについては「[GitHubでの執筆](/github/writing-on-github)」を参照してください。
+Issueを作成した後は、そのIssueにコメントを追加して会話を続けてください。 コラボレータあるいはTeamを@メンションして、コメントに注意を惹きつけることができます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 くわしい情報については「[GitHubでの執筆](/github/writing-on-github)」を参照してください。
 
 ![Issueのコメント](/assets/images/help/issues/issue-comment.png)
 
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index 115cd4d317..2fe8f14655 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -1,6 +1,6 @@
 ---
-title: 他のリポジトリへ Issue を移譲する
-intro: より適しているリポジトリに Issue を移動するため、オープン Issue を他のリポジトリに移譲できます。
+title: Transferring an issue to another repository
+intro: 'To move an issue to a better fitting repository, you can transfer open issues to other repositories.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/transferring-an-issue-to-another-repository
   - /articles/transferring-an-issue-to-another-repository
@@ -13,27 +13,29 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Issueの移譲
+shortTitle: Transfer an issue
 ---
-
 To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-同じユーザまたは Organization アカウントが所有するリポジトリ間においてのみ、Issue を移譲できます。 {% ifversion fpt or ghes or ghec %}プライベートリポジトリからパブリックリポジトリへIssueを移譲することはできません。{% endif %}
+You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}You can't transfer an issue from a private repository to a public repository.{% endif %}
 
-Issueを委譲する場合、コメントとアサインされた人は保持されます。 Issue のラベルとマイルストーンは保持されません。 このIssueは、ユーザー所有または組織全体のプロジェクトボードにとどまり、リポジトリのプロジェクトボードから削除されます。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。
+When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)."
 
-Issue でメンションされた人や Team は、Issue が新しいリポジトリに移譲されたことを知らせる通知を受け取ります。 当初の URL は、新しい Issue の URL にリダイレクトします。 新しいリポジトリの読み取り権限がない人には、アクセスできない新しいリポジトリに Issue が移譲されたことを知らせるバナーが表示されます。
+People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access.
 
-## 他のリポジトリへオープン Issue を移譲する
+## Transferring an open issue to another repository
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
-3. Issue のリストで、移譲したい Issue をクリックします。
-4. 右のサイドバーで [**Transfer this issue**] をクリックします。 ![Issue を移譲するボタン](/assets/images/help/repository/transfer-issue.png)
-5. [**Choose a repository**] ドロップダウンメニューで、Issue の移譲先にするリポジトリを選択します。 ![リポジトリセレクションを選択](/assets/images/help/repository/choose-a-repository.png)
-6. [**Transfer issue**] をクリックします。 ![Issue 移譲ボタン](/assets/images/help/repository/transfer-issue-button.png)
+3. In the list of issues, click the issue you'd like to transfer.
+4. In the right sidebar, click **Transfer issue**.
+![Button to transfer issue](/assets/images/help/repository/transfer-issue.png)
+5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to.
+![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png)
+6. Click **Transfer issue**.
+![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png)
 
 {% endwebui %}
 
@@ -49,8 +51,8 @@ gh issue transfer <em>issue</em> <em>{% ifversion ghes %}hostname/{% endif %}own
 
 {% endcli %}
 
-## 参考リンク
+## Further reading
 
-- 「[Issue について](/articles/about-issues)」
-- 「[セキュリティログをレビューする](/articles/reviewing-your-security-log)」
-- 「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)」
+- "[About issues](/articles/about-issues)"
+- "[Reviewing your security log](/articles/reviewing-your-security-log)"
+- "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)"
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
index d6e62f29c5..25bc309b45 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -25,4 +25,4 @@ Issue およびPull Requestダッシュボードは、すべてのページの
 
 ## 参考リンク
 
-- {% ifversion fpt or ghes or ghae or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listing the repositories you're watching](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
+- {% ifversion fpt or ghes or ghae or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}「[Watch しているリポジトリのリスト](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}」
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md
index 2725039d36..7f9fccd8f3 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md
@@ -29,7 +29,7 @@ topics:
 - タスクの複雑さを追跡する数値フィールド
 - タスクの優先度が低、中、高なのかを追跡するための単一選択フィールド
 - クイックノートを追跡するテキストフィールド
-- an iteration field to plan work week-by-week
+- 週ごとの作業を計画するための繰り返しフィールド
 
 ### 様々な観点からプロジェクトを見る
 
@@ -47,13 +47,13 @@ topics:
 
 詳しい情報については「[プロジェクトのビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。
 
-### Working with the project command palette
+### プロジェクトコマンドパレットでの作業
 
-You can use the project command palette to quickly change views or add fields. コマンドパレットは、カスタムキーボードショートカットを覚えておかなくてもいいようにガイドしてくれます。 詳しい情報については「[プロジェクトのビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。
+プロジェクトコマンドパレットを使って、素早くビューを切り替えたり、フィールドを追加したりできます。 コマンドパレットは、カスタムキーボードショートカットを覚えておかなくてもいいようにガイドしてくれます。 詳しい情報については「[プロジェクトのビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。
 
 ### プロジェクト管理タスクの自動化
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." You can also use the GraphQL API and {% data variables.product.prodname_actions %} to automate routine project management tasks. For more information, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)" and "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+プロジェクト（ベータ）は、組み込みのワークフローを提供します。 たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 GraphQL APIと{% data variables.product.prodname_actions %}を使って、ルーチンのプロジェクトタスクを自動化することもできます。 詳しい情報については「[プロジェクトの自動化](/issues/trying-out-the-new-projects-experience/automating-projects)」及び「[APIを使ったプロジェクトの管理](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)」を参照してください。
 
 ## プロジェクト（ベータ）と非ベータのプロジェクトの比較
 
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md
index 374fe7d144..b0fa4bc80d 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md
@@ -1,6 +1,6 @@
 ---
 title: プロジェクト（ベータ）の自動化
-intro: 'You can use built-in workflows or the API and {% data variables.product.prodname_actions %} to manage your projects.'
+intro: '組み込みのワークフロー、あるいはAPIと{% data variables.product.prodname_actions %}を使ってプロジェクトを管理できます。'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -17,13 +17,13 @@ topics:
 
 ## はじめに
 
-You can add automation to help manage your project. Projects (beta) includes built-in workflows that you can configure through the UI. Additionally, you can write custom workflows with the GraphQL API and {% data variables.product.prodname_actions %}.
+プロジェクトの管理に役立つ自動化を追加できます。 プロジェクト（ベータ）には、UIを通じて設定できる組み込みのワークフローが含まれています。 加えて、GraphQL APIと{% data variables.product.prodname_actions %}でカスタムのワークフローを書くことができます。
 
-## Built-in workflows
+## 組み込みのワークフロー
 
 {% data reusables.projects.about-workflows %}
 
-You can enable or disable the built-in workflows for your project.
+プロジェクトでは、組み込みのワークフローを有効化あるいは無効化できます。
 
 {% data reusables.projects.enable-basic-workflow %}
 
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
index 1f46ea5940..849048728c 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
@@ -49,7 +49,7 @@ IssueとPull Requestには、コラボレータと容易にコミュニケーシ
 
 You can automate tasks to spend less time on busy work and more time on the project itself. 手動でやることを覚えておく必要が減れば、それだけプロジェクトは耐震の状態に保たれるようになります。
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done."
+プロジェクト（ベータ）は、組み込みのワークフローを提供します。 たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。
 
 Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review."
 
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index 1a3f4355df..7e2f24fabc 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -152,7 +152,7 @@ You can later edit the drop down options for single select and iteration fields.
 
 {% data reusables.projects.about-workflows %}
 
-You can enable or disable the built-in workflows for your project.
+プロジェクトでは、組み込みのワークフローを有効化あるいは無効化できます。
 
 {% data reusables.projects.enable-basic-workflow %}
 
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index 52fbe44335..18f9b8bc2e 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -22,7 +22,7 @@ topics:
 
 **メモ:** プルリクエストを使う際には以下のことを念頭に置いてください:
 * [共有リポジトリモデル](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)で作業をしている場合、プルリクエストにはトピックブランチを使うことをおすすめします。 ブランチあるいはコミットからプルリクエストを送ることもできますが、トピックブランチを使えば提案した変更を更新する必要がある場合、フォローアップのコミットをプッシュできます。
-* プルリクエストにコミットをプッシュする場合、フォースプッシュはしないでください。 Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
+* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
 
 {% endnote %}
 
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index 85c154a11d..e49a1ea145 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -17,7 +17,7 @@ topics:
 
 リポジトリのフォークはリポジトリのコピーと似ていますが、次の 2 つの大きな違いがあります。
 
-* プルリクエストを使ってユーザが所有するフォークからの変更をオリジナルのリポジトリ（*上流*のリポジトリとも呼ばれます）に提案できます。
+* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository.
 * 上流のリポジトリと自分のフォークを同期させることで、上流のリポジトリからの変更を自分のローカルフォークへ持ち込めます。
 
 {% data reusables.repositories.you-can-fork %}
diff --git a/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md b/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
index acb289f986..5d51bf49fe 100644
--- a/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
@@ -5,8 +5,8 @@ permissions:
   actions: read|write|none
   checks: read|write|none
   contents: read|write|none
-  deployments: read|write|none
-  id-token: read|write|none
+  deployments: read|write|none{% ifversion fpt or ghec %}
+  id-token: read|write|none{% endif %}
   issues: read|write|none
   discussions: read|write|none
   packages: read|write|none
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 1cac04a053..1b4d54ed97 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -148,6 +148,7 @@ translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resour
 translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags
 translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
 translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags
+translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md,broken liquid tags
 translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489
 translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
 translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index 6f18634301..19c4857233 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -38,7 +38,7 @@ Se você for integrante de um {% data variables.product.prodname_emu_enterprise
 1. Pergunte o nome do usuário da pessoa que você está convidando a colaborar.{% ifversion fpt or ghec %} Caso a pessoa não tenha um nome de usuário ainda, deve se inscrever em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Inscrever-se em uma nova conta {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)".{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%}
 {% data reusables.repositories.click-collaborators-teams %}
 1. Clique em **Convidar um colaborador**. ![Botão "Convidar um colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png)
 2. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field-user.png)
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index f9c9852e15..c88edc9073 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -30,7 +30,7 @@ Apesar de as bifurcações de repositórios privados serem excluídas quando um
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
 4. À direita do colaborador que deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Botão para remover o colaborador](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 8a53be2b9a..c8f4163bed 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -21,8 +21,8 @@ shortTitle: Remover-se
 ---
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
-2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
+2. Na seção "código, planejamento e automação" na barra lateral, clique em **Repositórios de {% octicon "repo" aria-label="The repo icon" %}**.
 {% else %}
 2. Na barra lateral esquerda, clique em **Repositories** (Repositórios). ![Guia Repositories (Repositórios)](/assets/images/help/settings/settings-sidebar-repositories.png)
 {% endif %}
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index 474fd1449c..1a8c5abd63 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -14,5 +14,5 @@ shortTitle: Gerenciando o tamanho da sua aba
 Se você considerar que a indentação em abas no código interpretado em {% data variables.product.product_name %} demanda muito tempo, ou muito pouco espaço, você poderá alterar isto nas suas configurações.
 
 {% data reusables.user_settings.access_settings %}
-1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+1. Na barra lateral esquerda, clique em **Aparência de {% octicon "paintbrush" aria-label="The paintbrush icon" %}**.
 2. Em "Preferência do tamanho da aba", selecione o menu suspenso e escolha sua preferência. ![Botão de preferência do tamanho da aba](/assets/images/help/settings/tab-size-preference.png)
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index 0b050c4a08..3897143cc3 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -22,7 +22,7 @@ Você pode querer usar um tema escuro para reduzir o consumo de energia em certo
 
 {% note %}
 
-**Nota:** Os temas para daltônicos e os temas com alto contraste de luz estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".
+**Observação:** Os temas coloridos estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index e907da9c49..40fbd049e1 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -69,7 +69,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Build with Gradle
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: build
 ```
@@ -106,7 +106,7 @@ steps:
   - name: Validate Gradle wrapper
     uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
   - name: Run the Gradle package task
-    uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+    uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
     with:
       arguments: -b ci.gradle package
 ```
@@ -135,7 +135,7 @@ steps:
   - name: Validate Gradle wrapper
     uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
   - name: Build with Gradle
-    uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+    uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
     with:
       arguments: build
   - uses: actions/upload-artifact@v2
diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index bd68979d73..71d718f64c 100644
--- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -47,7 +47,7 @@ Se você definir o `entrypoint` em um arquivo de metadados de uma ação, ele ir
 
 A instrução do `ENTRYPOINT` do Docker tem forma de _shell_ e forma de _exec_. A documentação do `ENTRYPOINT` do docker recomenda o uso da forma _exec_ da instrução do `ENTRYPOINT`. Para obter mais informações sobre as formas _exec_ e _shell_, consulte a referência ENTRYPOINT [](https://docs.docker.com/engine/reference/builder/#entrypoint) na documentação do Docker.
 
-You should not use `WORKDIR` to specify your entrypoint in your Dockerfile. Instead, you should use an absolute path. For more information, see [WORKDIR](#workdir).
+Você não deve usar `WORKDIR` para especificar seu ponto de entrada no seu arquivo Docker. Em vez disso, você edverá usar um caminho absoluto. Para obter mais informações, consulte [WORKDIR](#workdir).
 
 Se você configurar o seu contêiner para usar a forma _exec_ da instrução `ENTRYPOINT`, os `args` configurados no arquivo de metadados da ação não serão executados em um shell do comando. Se os `args` da ação contiverem uma variável do ambiente, esta não será substituída. Por exemplo, usar o formato _exec_ a seguir não imprimirá o valor armazenado em `$GITHUB_SHA`. Em vez disso, imprimirá `$GITHUB_SHA`.
 
diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index d491d5c4f1..c55b527e76 100644
--- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 4
 
 ## Sobre sintaxe YAML para o {% data variables.product.prodname_actions %}
 
-All actions require a metadata file. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
+Todas as ações exigem um arquivo de metadados. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. Os dados no arquivo de metadados definem as entradas, saídas e executam a configuração para sua ação.
 
 Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que é YAML, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
@@ -41,7 +41,7 @@ Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que
 
 **Opcional**: parâmetros de entrada permitem que você especifique os dados que a ação espera usar no momento da execução. O {% data variables.product.prodname_dotcom %} armazena parâmetros como variáveis de ambiente. Identificações de entrada com letras maiúsculas são alteradas para letras minúsculas no momento da execução. Recomenda-se usar identificações de entrada com letras minúsculas.
 
-### Example: Specifying inputs
+### Exemplo: Especificando entradas
 
 Este exemplo configura duas entradas: numOctocats e octocatEyeColor. A entrada numOctocats não é necessária e assumirá o valor '1'. A entrada octocatEyeColor é necessária e não tem valor padrão. Arquivos de fluxo de trabalho que usam essa ação devem usar a palavra-chave `with` (com) para definir um valor de entrada para octocatEyeColor. Para obter mais informações sobre a sintaxe `with` (com), consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)".
 
@@ -84,13 +84,13 @@ Por exemplo, se um fluxo de trabalho definiu as entradas `numOctocats` e `octoca
 
 **Opcional** Se o parâmetro de entrada for usado, esta `string` será registrada como uma mensagem de aviso. Você pode usar este aviso para notificar os usuários de que o valor de entrada está obsoleto e mencionar outras alternativas.
 
-## `outputs` for Docker container and JavaScript actions
+## `sapidas` para o contêiner do Docker e ações do JavaScript
 
 **Opcional** Os parâmetros de saída permitem que você declare os dados definidos por uma ação. As ações executadas posteriormente em um fluxo de trabalho podem usar os dados de saída definidos em ações executadas anteriormente.  Por exemplo, se uma ação executou a adição de duas entradas (x + y = z), a ação poderia usar o resultado da soma (z) como entrada em outras ações.
 
 Se você não declarar uma saída no seu arquivo de metadados de ação, você ainda poderá definir as saídas e usá-las no seu fluxo de trabalho. Para obter mais informações sobre a definição de saídas em uma ação, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
 
-### Example: Declaring outputs for Docker container and JavaScript actions
+### Exemplo: Declarando saídas para o contêiner do Docker e ações do JavaScript
 
 ```yaml
 saídas:
@@ -447,7 +447,7 @@ Se você precisar passar variáveis de ambiente para uma ação, certifique-se d
 
 Para obter mais informações sobre o uso da instrução `CMD` com {% data variables.product.prodname_actions %}, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)".
 
-#### Example: Defining arguments for the Docker container
+#### Exemplo: Definir argumentos para o contêiner do Docker
 
 {% raw %}
 ```yaml
@@ -465,7 +465,7 @@ runs:
 
 Você pode usar uma cor e o ícone da [Pena](https://feathericons.com/) para criar um selo para personalizar e distinguir a sua ação. Os selos são exibidos ao lado do nome da sua ação em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-### Example: Configuring branding for an action
+### Exemplo: Configurar a marca para uma ação
 
 ```yaml
 branding:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index e2b4a004fb..ebabfae7f8 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -90,8 +90,12 @@ Este procedimento demonstra como criar a conta de serviço para sua integração
   ```
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
     --member=serviceAccount:$SA_EMAIL \
-    --role=roles/container.admin \
-    --role=roles/storage.admin \
+    --role=roles/container.admin
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+    --member=serviceAccount:$SA_EMAIL \
+    --role=roles/storage.admin
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+    --member=serviceAccount:$SA_EMAIL \
     --role=roles/container.clusterViewer
   ```
   {% endraw %}
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 8572081125..d5a61922e2 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -29,7 +29,7 @@ Ao atualizar seus fluxos de trabalho para usar tokens do OIDC, você pode adotar
 
 - **Sem segredos na nuvem**: Você não vai precisar duplicar suas credenciais da nuvem como segredos de {% data variables.product.prodname_dotcom %} de longa duração. Em vez disso, você pode configurar a confiança do OIDC no seu provedor de nuvem, e, em seguida, atualizar seus fluxos de trabalho para solicitar um token de acesso curto do provedor de nuvem por meio do OIDC.
 - **Autenticação e gestão de autorização**: Você tem mais controle granular sobre como fluxos de trabalho podem usar credenciais, usando a autenticação de seu provedor de nuvem (authN) e ferramentas de autorização (authZ) para controlar o acesso a recursos na nuvem.
-- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires.
+- **Girando credenciais**: Com o OIDC, seu provedor de nuvem emite um token de acesso de curta duração que só é válido para uma única execução de um trabalho e, posteriormente, vence automaticamente.
 
 ### Introdução ao OIDC
 
@@ -38,7 +38,7 @@ O diagrama a seguir fornece uma visão geral de como o provedor OIDC de {% data
 ![Diagrama do OIDC](/assets/images/help/images/oidc-architecture.png)
 
 1. No seu provedor de nuvem, crie uma confiança do OIDC entre a sua função na nuvem e o(s) seu(s) fluxo(s) de trabalho {% data variables.product.prodname_dotcom %} que precisam acessar a nuvem.
-2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. Esse token contém várias reivindicações para estabelecer uma identidade de segurança reforçada e verificável sobre o fluxo de trabalho específico que está tentando autenticar.
+2. Toda vez que o seu trabalho é executado, o provedor OIDC de {% data variables.product.prodname_dotcom %} gera um token de OIDC automaticamente. Esse token contém várias reivindicações para estabelecer uma identidade de segurança reforçada e verificável sobre o fluxo de trabalho específico que está tentando autenticar.
 3. Você pode incluir um passo ou ação no seu trabalho para solicitar este token do provedor do OIDC de {% data variables.product.prodname_dotcom %}, e apresentá-lo ao provedor da nuvem.
 4. Uma vez que o provedor de nuvem valida as reivindicações apresentadas no token, ele irá fornecer, posteriormente, um token de acesso à nuvem de curta duração que está disponível apenas para a duração do trabalho.
 
@@ -51,7 +51,7 @@ Ao configurar sua nuvem para confiar no provedor do OIDC de {% data variables.pr
 
 ### Entendendo o token do OIDC
 
-Each job requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. When the job runs, the OIDC token is presented to the cloud provider. Para validar o token, o provedor de nuvem verifica se o assunto do token do OIDC e outras reivindicações correspondem às condições que foram pré-configuradas na definição de confiança do OIDC da função da nuvem.
+Cada trabalho solicita um token do OIDC de {% data variables.product.prodname_dotcom %}, que responde com um token web do JSON gerado automaticamente (JWT) que é único para cada trabalho de fluxo de trabalho em que é gerado. Quando o trabalho é executado, o token de OIDC é apresentado ao provedor de nuvem. Para validar o token, o provedor de nuvem verifica se o assunto do token do OIDC e outras reivindicações correspondem às condições que foram pré-configuradas na definição de confiança do OIDC da função da nuvem.
 
 O exemplo a seguir do token do OIDC usa um assunto (`sub`) que faz referência a um ambiente de trabalho chamado `prod` no repositório `octo-org/octo-repo`.
 
@@ -147,7 +147,7 @@ Além disso, seu provedor de nuvem poderia permitir que você atribuísse uma fu
 
 ### Exemplos
 
-Os exemplos a seguir demonstram como usar "Assunto" como uma condição. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. As seguintes secções descrevem alguns assuntos comuns que você pode usar.
+Os exemplos a seguir demonstram como usar "Assunto" como uma condição. O [assunto](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) usa informações do contexto [trabalho`` trabalho da execução do fluxo de trabalho](/actions/learn-github-actions/contexts#job-context) e orienta o seu provedor na nuvem que as solicitações do token de acesso só podem ser concedidas para solicitações de fluxos de trabalho em execução em branches e ambientes específicos. As seguintes secções descrevem alguns assuntos comuns que você pode usar.
 
 #### Filtragem para um ambiente específico
 
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 60fcaa150a..3f672a99b9 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -19,7 +19,7 @@ topics:
 
 O OpenID Connect (OIDC) permite aos seus fluxos de trabalho de {% data variables.product.prodname_actions %} efetuar a autenticação com um HashiCorp Vault para recuperar segredos.
 
-This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault.
+Este guia fornece uma visão geral sobre como configurar o cofre HashiCorp para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada e mostra como usar essa configuração na ação [hashicorp/vault-action](https://github.com/hashicorp/vault-action) para recuperar segredos do cofre HashiCorp.
 
 ## Pré-requisitos
 
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index b1bd8075ff..52cc87e50c 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
 
 You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 1. Click **New self-hosted runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
@@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
 
 You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 1. Click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 
@@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use
 
 New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
 1. Click **Add new**, then click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
-{% ifversion ghec or ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
 
 {% data reusables.github-actions.self-hosted-runner-public-repo-access %}
-{% endif %}
 
 ### Making enterprise runners available to repositories
 
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 6bd6e9ab96..d756d87773 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -32,7 +32,7 @@ Cada solução tem certas especificações que podem ser importantes para consid
 | Tempo de execução                          | Kubernetes                                                                                    | VMs do Linux e do Windows                                                            |
 | Nuvens compatíveis                         | Azure, Amazon Web Services, Google Cloud Platform, nos locais                                 | Amazon Web Services                                                                  |
 | Onde os executores podem ser dimensionados | Níveis de empresa, organização e repositório. Por etiqueta do executor e grupo de executores. | Níveis de organização e repositório. Por etiqueta do executor e grupo de executores. |
-| How runners can be scaled                  | Webhook events, Scheduled, Pull-based                                                         | Webhook events, Scheduled (org-level runners only)                                   |
+| Como os executores podem ser dimensionados | Webhook events, Scheduled, Pull-based                                                         | Webhook events, Scheduled (org-level runners only)                                   |
 
 ## Usaar executores efêmeros para dimensionamento automático
 
@@ -54,25 +54,25 @@ O serviço {% data variables.product.prodname_actions %} irá cancelar o resgist
 
 {% endnote %}
 
-## Controlling runner software updates on self-hosted runners
+## Controlando atualizações de software dos executores em executores auto-hospedados
 
-By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available.  If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released.  Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
+Por padrão, os executores auto-hospedados realizarão automaticamente uma atualização de software sempre que uma nova versão do executor estiver disponível.  Se você usar executoresefêmeros em contêineres, isso pode gerar a atualizações de software repetidas quando uma nova versão do executor for lançada.  A desabilitação das atualizações automáticas permite que você atualize a versão do executor na imagem do contêiner diretamente no seu próprio agendamento.
 
-If you want to turn off automatic software updates and install software updates yourself, you can specify the `--disableupdate` parameter when starting the runner.  Por exemplo:
+Se você deseja desativar as atualizações automáticas de software e instalar as atualizações de software, você poderá especificar o parâmetro `--disableupdate` ao iniciar o executor.  Por exemplo:
 
 ```shell
 ./run.sh --disableupdate
 ```
 
-If you disable automatic updates, you must still update your runner version regularly.  New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software.  The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
+Se você desabilitar as atualizações automáticas, você ainda deverá atualizar sua versão do executor regularmente.  A nova funcionalidade em {% data variables.product.prodname_actions %} exige alterações no serviço de {% data variables.product.prodname_actions %} service _e_ no software do executor.  O executor pode não conseguir de processar corretamente os trabalhos que aproveitam novas funcioanlidades em {% data variables.product.prodname_actions %} sem a atualização de um software.
 
-If you disable automatic updates, you will be required to update your runner version within 30 days of a new version being made available.  You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). Para obter mais informações, consulte “[Configurando notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)".
+Se você desabilitar as atualizações automáticas, será necessário atualizar a versão do seu executor no prazo de 30 dias a contar da nova versão disponível.  Você deverá assinar para receber as notificações de versões no repositório [`actions/runner` repository](https://github.com/actions/runner/releases). Para obter mais informações, consulte “[Configurando notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)".
 
-For instructions on how to install the latest runner version, see the installation instructions for [the latest release](https://github.com/actions/runner/releases).
+Para obter instruções sobre como instalar a versão mais recente do executor, consulte as instruções de instalação referentes [à última versão](https://github.com/actions/runner/releases).
 
 {% note %}
 
-**Note:** If you do not perform a software update within 30 days, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner.  In addition, if a critical security update is required, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner until it has been updated.
+**Observação:** Se você não executar uma atualização de software em 30 dias, o serviço de {% data variables.product.prodname_actions %} não irá colocar trabalhos na fila para o seu executor.  Além disso, se uma atualização crítica de segurança for necessária, o serviço de {% data variables.product.prodname_actions %} não colocará os trabalhos na fila do seu executor até que ele seja atualizado.
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index f4f6d9c310..7c915d6208 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -46,7 +46,7 @@ Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão
 
 Ao criar um grupo, você deverá escolher uma política que defina quais repositórios têm acesso ao grupo do executor.
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
@@ -61,12 +61,11 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Na seção "Executores auto-hospedados", clique em **Adicionar novo** e, em seguida, **Novo grupo**.
+1. Em {% ifversion ghes > 3.1 or ghae %}"Executores"{% elsif ghes < 3.2 %}"Executores auto-hospedados"{% endif %}, clique em **Adicionar novo** e, em seguida, **Novo grupo**.
 
     ![Adicionar grupo de executor](/assets/images/help/settings/actions-org-add-runner-group.png)
 1. Insira um nome para o seu grupo de executor e atribua uma política para acesso ao repositório.
@@ -95,7 +94,7 @@ Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão
 
 Ao criar um grupo, você deve escolher uma política que defina quais organizações têm acesso ao grupo de executores.
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -113,8 +112,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -144,7 +142,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç
 ## Alterar a política de acesso de um grupo de executores auto-hospedados
 
 Você pode atualizar a política de acesso de um grupo de executores ou renomear um grupo de executores.
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
 1. Modifique as opções de acesso ou altere o nome do grupo dp executor.
@@ -158,8 +156,7 @@ Você pode atualizar a política de acesso de um grupo de executores ou renomear
    Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
 {% endif %}
 
@@ -181,17 +178,18 @@ Não foi possível encontrar nenhum grupo de executor auto-hospedado denominado
 ## Mover um executor auto-hospedado para um grupo
 
 Se você não especificar o grupo de um executor durante o processo de registro, seus novos executores auto-hospedados são automaticamente atribuídos ao grupo padrão e poderão ser transferidos para outro grupo.
-{% ifversion ghec or ghes > 3.1 or ghae %}
+
 {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 1. Na lista de "Executores", clique no executor que você deseja configurar.
 2. Selecione o menu suspenso do grupo do executor.
 3. Em "Transferir executor para o grupo", escolha um grupo de destino para o executor.
-{% endif %}
-{% ifversion ghes < 3.2 or ghae %}
-1. Na seção "executores auto-hospedados" da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png)
+{% elsif ghae or ghes < 3.4 %}
+1. Na seção {% ifversion ghes > 3.1 or ghae %}"Grupos de executores"{% elsif ghes < 3.2 %}"Executores auto-hospedados"{% endif %} da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png)
 2. Marque a caixa de seleção ao lado do executor auto-hospedado e, em seguida, clique em **Mover para o grupo** para ver os destinos disponíveis. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move.png)
 3. Para mover o executor, clique no grupo de destino. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
+
 ## Remover um grupo de executor auto-hospedado
 
 Os executores auto-hospedados são retornados automaticamente ao grupo-padrão quando seu grupo é removido.
@@ -201,8 +199,7 @@ Os executores auto-hospedados são retornados automaticamente ao grupo-padrão q
 1. Na lista de grupos, à direita do grupo que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
 2. Para remover o grupo, clique em **Remover grupo**.
 3. Revise os avisos de confirmação e, em seguida, clique em **Remover este grupo de executores**.
-{% endif %}
-{% ifversion ghes < 3.2 or ghae %}
+{% elsif ghes < 3.2 %}
 1. Na seção "Executores auto-hospedados" da página de configurações, localize o grupo que você deseja excluir e clique no botão {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} . ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
 1. Para remover o grupo, clique em **Remover grupo**. ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-remove.png)
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index cbc55ec1c3..0230c45041 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -30,20 +30,20 @@ shortTitle: Remover executores auto-hospedados
 Para remover um executor auto-hospedado de um repositório de usuário, você deve ser o proprietário do repositório. Para um repositório da organização, você deve ser um proprietário da organização ou ter acesso de administrador ao repositório. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)."
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
+
 ## Remover um executor de uma organização
 
 {% note %}
@@ -57,19 +57,20 @@ Para remover um executor auto-hospedado de um repositório de usuário, você de
 Para remover um executor auto-hospedado de uma organização, você deve ser um proprietário da organização. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)."
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+{% ifversion fpt or ghes > 3.3 or ghec %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% else %}
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
+
 ## Remover um executor de uma empresa
 
 {% ifversion fpt %}
@@ -85,19 +86,17 @@ Se você usar
 
 {% endnote %}
 
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+Para remover um executor auto-hospedado de uma empresa, você deverá ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte [as APIs do GitHub Actions da administração da empresa](/rest/reference/enterprise-admin#github-actions).
 
-{% ifversion ghec %}
-Para remover um executor auto-hospedado de uma conta corporativa, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como adicionar um executor auto-hospedado com a API REST, consulte [as APIs do GitHub Actions da administração da empresa](/rest/reference/enterprise-admin#github-actions).
+{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% elsif ghae or ghes %}
-Para remover um executor auto-hospedado no nível da empresa de
-{% data variables.product.product_location %}, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado.
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 573436c429..ceb170b4a8 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -19,13 +19,13 @@ Para obter informações sobre como usar etiquetas para encaminhar trabalhos par
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
 ## Criar etiquetas personalizadas
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
  1. Na seção "Etiquetas", clique em {% octicon "gear" aria-label="The Gear icon" %}.
  1. No campo "Encontrar ou criar uma etiqueta", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
@@ -34,35 +34,38 @@ Para obter informações sobre como usar etiquetas para encaminhar trabalhos par
 
 O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
+
 ## Atribuir uma etiqueta a um executor auto-hospedado
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.runner-label-settings %}
   1. Para atribuir uma etiqueta ao executor auto-hospedado, no campo "Localizar ou criar uma etiqueta", clique na etiqueta.
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
 1. Clique em uma etiqueta a ser atribuída ao seu executor auto-hospedado.
 {% endif %}
+
 ## Remover uma etiqueta personalizada de um executor auto-hospedado
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.runner-label-settings %}
   1. No campo "Encontre ou crie uma etiqueta", as etiquetas atribuídas são marcadas com a
 Ícone de {% octicon "check" aria-label="The Check icon" %}. Clique em uma etiqueta marcada para cancelar a atribuição do seu executor auto-hospedado.
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
 1. Clique na etiqueta atribuída para removê-la do seu executor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
+
 ## Usar o script de configuração para criar e atribuir rótulos
 
 Você pode usar o script de configuração no executor auto-hospedado para criar e atribuir etiquetas personalizadas. Por exemplo, este comando atribui ao executor auto-hospedado uma etiqueta denominada `gpu`.
diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
index 652b73305d..6ea946014c 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
@@ -73,7 +73,7 @@ A tabela a seguir indica onde cada contexto e função especial pode ser utiliza
 | <code>concorrência</code>  | <code>github, entradas</code>  |                            |
 | <code>env</code>  | <code>github, segredos, entradas</code>  |                            |
 | <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, necessidades, estratégia, matriz, entradas</code>  |                            |
-| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, necessidades, estratégia, matriz, entradas</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, necessidades, estratégia, matriz, segredos, entradas</code>  |                            |
 | <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, necessidades, estratégia, matrix, env, segredos, entradas</code>  |                            |
 | <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, necessidades, estratégia, matrix, trabalho, executor, env, segredos, entradas</code> |                            |
 | <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
@@ -393,7 +393,7 @@ O contexto `etapas` contém informações sobre as etapas do trabalho atual que
 | Nome da propriedade                                 | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                    |
 | --------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `steps`                                             | `objeto` | Esse contexto altera cada etapa em um trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. Este objeto contém todas as propriedades listadas abaixo.                                                                                                                                                                                                  |
-| `steps.<step_id>.outputs`                     | `objeto` | Conjunto de saídas definidas para a etapa. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."                                                                                                                                |
+| `steps.<step_id>.outputs`                     | `objeto` | Conjunto de saídas definidas para a etapa. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)".                                                                                                            |
 | `steps.<step_id>.conclusion`                  | `string` | O resultado de uma etapa concluída após [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`.     |
 | `steps.<step_id>.outcome`                     | `string` | O resultado de uma etapa concluída antes de [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`. |
 | `steps.<step_id>.outputs.<output_name>` | `string` | Valor de uma saída específica.                                                                                                                                                                                                                                                                                                                                               |
diff --git a/translations/pt-BR/content/actions/learn-github-actions/expressions.md b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
index 3fa5078735..2c7a72a544 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
@@ -50,12 +50,12 @@ env:
 
 Como parte da expressão, você pode usar os tipos de dados `boolean`, `null`, `number` ou `string`.
 
-| Tipo de dados | Valor do literal                                                                                                                                                                                                                                                                                                                      |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `boolean`     | `true` ou `false`                                                                                                                                                                                                                                                                                                                     |
-| `null`        | `null`                                                                                                                                                                                                                                                                                                                                |
-| `number`      | Qualquer formato de número aceito por JSON.                                                                                                                                                                                                                                                                                           |
-| `string`      | You don't need to enclose strings in `{% raw %}${{{% endraw %}` and `{% raw %}}}{% endraw %}`. However, if you do, you must use single quotes (`'`) around the string. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. |
+| Tipo de dados | Valor do literal                                                                                                                                                                                                                                                                                                                           |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `boolean`     | `true` ou `false`                                                                                                                                                                                                                                                                                                                          |
+| `null`        | `null`                                                                                                                                                                                                                                                                                                                                     |
+| `number`      | Qualquer formato de número aceito por JSON.                                                                                                                                                                                                                                                                                                |
+| `string`      | Você não precisa anexar strings em `{% raw %}${{{% endraw %}` e `{% raw %}}}{% endraw %}`. No entanto, se o fizer, você deverá usar aspas simples (`'`) em torno da string. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. |
 
 #### Exemplo
 
diff --git a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 16fe3ea193..7e3f731724 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -47,7 +47,7 @@ Você pode pesquisar ações diretamente no seu editor do seu fluxo de trabalho
 
 Você pode adicionar uma ação ao seu fluxo de trabalho fazendo referência à ação no arquivo do seu fluxo de trabalho.
 
-You can view the actions referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+Você pode visualizar as ações referenciadas em seus fluxos de trabalho de {% data variables.product.prodname_actions %} como dependências no gráfico de dependências do repositório que contém seus fluxos de trabalho. Para obter mais informações, consulte “[Sobre o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”.
 
 ### Adicionando uma ação de {% data variables.product.prodname_marketplace %}
 
diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
index ac13eaa5ff..7743a83067 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
@@ -259,4 +259,4 @@ Para entender como a cobrança funciona para {% data variables.product.prodname_
 ## Leia mais
 
 {% ifversion ghec or ghes or ghae %}
-- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %}
+- "[Sobre {% data variables.product.prodname_actions %} para as empresas](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %}
diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index a949fddb04..5ac68ab8b2 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -18,12 +18,12 @@ shortTitle: Cobrança do fluxo de trabalho & limites
 
 ## Sobre a cobrança do {% data variables.product.prodname_actions %}
 
-{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+{% data reusables.repositories.about-github-actions %} Para obter mais informações, consulte "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" e "[Sobre {% data variables.product.prodname_actions %} para empresas](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
 
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.actions-billing %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 {% else %}
-GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+O uso do GitHub Actions é grátis para instâncias de {% data variables.product.prodname_ghe_server %} que usam executores auto-hospedados. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 {% endif %}
 
 
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index a5a0da38a8..54770117e6 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -63,7 +63,7 @@ O Jenkins usa diretivas para gerenciar os _Declarative Pipelines_. Essas diretiv
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`ambiente`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                                                                           | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                             | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                                                                                                                                                                                                                                                           |
-| [`parâmetros`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                          | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| [`parâmetros`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                          | [`entradas`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`saídas`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | [`gatilhos`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                                                              | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore) <br> [<code>on.<pull_request\>.<branches\></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) |
 | [`aciona { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                                         | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | [Sintaxe cron do Jenkins](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)                                                                                                                                                                                                                                                                                              | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index ff449845c9..d4617e6230 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -96,7 +96,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env:
@@ -167,7 +167,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env:
@@ -246,7 +246,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env: {% raw %}
diff --git a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
index b7825a578f..cbb4a4a810 100644
--- a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
@@ -85,8 +85,9 @@ A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão
 | ações        | leitura/gravação                    | nenhum                            | leitura                                            |
 | Verificações | leitura/gravação                    | nenhum                            | leitura                                            |
 | Conteúdo     | leitura/gravação                    | leitura                           | leitura                                            |
-| Implantações | leitura/gravação                    | nenhum                            | leitura                                            |
-| id-token     | leitura/gravação                    | nenhum                            | leitura                                            |
+| Implantações | leitura/gravação                    | nenhum                            | read |{% ifversion fpt or ghec %}
+| id-token     | leitura/gravação                    | nenhum                            | read 
+{% endif %}
 | Problemas    | leitura/gravação                    | nenhum                            | leitura                                            |
 | metadados    | leitura                             | leitura                           | leitura                                            |
 | pacotes      | leitura/gravação                    | nenhum                            | leitura                                            |
diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
index 65f2a399db..01feec3181 100644
--- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
@@ -356,30 +356,30 @@ Os segredos são limitados a 64 kB. Para usar segredos maiores que 64 kB, você
 {% endraw %}
 
 
-## Storing Base64 binary blobs as secrets
+## Armazenar Blobs binários de Base64 como segredos
 
-You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
+Você pode usar a codificação de Base64 para armazenar pequenos blobs binários como segredos. Em seguida, você pode fazer referência ao segredo no seu fluxo de trabalho e decodificá-lo para usar no executor. Para os limites de tamanho, consulte ["Limites para segredos"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
 
 {% note %}
 
-**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
+**Observação**: Observe que o Base64 só converte números binários em texto e não substitui a criptografia real.
 
 {% endnote %}
 
-1. Use `base64` to encode your file into a Base64 string. Por exemplo:
+1. Use `base64` para codificar seu arquivo em uma string de Base64. Por exemplo:
 
    ```
    $ base64 -i cert.der -o cert.base64
    ```
 
-1. Create a secret that contains the Base64 string. Por exemplo:
+1. Crie um segredo que contenha a string de Base64. Por exemplo:
 
    ```
    $ gh secret set CERTIFICATE_BASE64 < cert.base64
    ✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
    ```
 
-1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`.  Por exemplo:
+1. Para acessar a string de Base64 do seu executor, transforme segredo em `base64 --decode`.  Por exemplo:
 
    ```yaml
    name: Retrieve Base64 secret
diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md
index 72a7a8808f..57905a4c44 100644
--- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -202,6 +202,10 @@ Os mesmos princípios descritos acima para o uso de ações de terceiros também
 {% data reusables.actions.outside-collaborators-internal-actions %} Para obter mais informações, consulte "[Compartilhando ações e fluxos de trabalho com a sua empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)".
 {% endif %}
 
+## Usando os Scorecards OpenSSF para proteger fluxos de trabalho
+
+[Scorecards](https://github.com/ossf/scorecard) é uma ferramenta de segurança automatizada que sinaliza práticas arriscadas da cadeia de suprimentos. Você pode usar a [ação Scorecards](https://github.com/marketplace/actions/ossf-scorecard-action) e o [fluxo de trabalho iniciante](https://github.com/actions/starter-workflows) para seguir as práticas recomendadas de segurança. Uma vez configurada, a ação Scorecards é executada automaticamente nas alterações de repositórios e alerta de desenvolvedores sobre práticas arriscadas em cadeia de suprimentos que usam a experiência de digitalização embutida do código. O projeto Scorecards executa um número de verificações, incluindo ataques de injeção de script, permissões de token e ações fixadas.
+
 ## Possível impacto de um executor comprometido
 
 Essas seções consideram alguns das etapas que um invasor pode dar se for capaz de executar comandos maliciosos em um executor de {% data variables.product.prodname_actions %}.
diff --git a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md
index 9a6a8a5595..33d61ce792 100644
--- a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md
@@ -34,7 +34,7 @@ Se você reutilizar um fluxo de trabalho de um repositório diferente, todas as
 
 Quando um fluxo de trabalho reutilizável é acionado por um fluxo de trabalho de chamadas, o contexto `github` está sempre associado ao fluxo de trabalho de chamada. O fluxo de trabalho chamado tem acesso automaticamente a `github.token` e `secrets.GITHUB_TOKEN`. Para obter mais informações sobre o contexto do github ``, consulte "[Contexto e sintaxe de expressão para o GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
-You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+Você pode visualizar os fluxos de trabalho referenciados nos seus fluxos de trabalho de {% data variables.product.prodname_actions %} como dependências no gráfico de dependências do repositório que contém seus fluxos de trabalho. Para obter mais informações, consulte “[Sobre o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”.
 
 ### Fluxos de trabalho e fluxos de trabalho iniciais reutilizáveis
 
diff --git a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
index bf4729df01..d25ca23a33 100644
--- a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
@@ -128,9 +128,9 @@ Use a chave `on` para especificar quais eventos acionam o seu fluxo de trabalho.
 {% data reusables.github-actions.workflow-dispatch-inputs %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-## Defining inputs, outputs, and secrets for reusable workflows
+## Definindo entradas, saídas e segredos para fluxos de trabalho reutilizáveis
 
-You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+É possível definir entradas e segredos que um fluxo de trabalho reutilizável deve receber de um fluxo de trabalho chamado. Também é possível especificar saídas que um fluxo de trabalho reutilizável disponibilizará para um fluxo de trabalho chamado. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/using-workflows/reusing-workflows)".
 
 {% endif %}
 
@@ -140,7 +140,7 @@ As informações sobre o evento que desencadeou uma execução de fluxo de traba
 
 ### Visualizando todas as propriedades de um evento
 
-Referência à documentação de evento de webhook para propriedades comuns e cargas de exemplo. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+Referência à documentação de evento de webhook para propriedades comuns e cargas de exemplo. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)".
 
 Você também pode imprimir o contexto inteiro de `github.event` para ver quais propriedades estão disponíveis para o evento que acionou o seu fluxo de trabalho:
 
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 4ca6ad2045..c92dd9632d 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -92,7 +92,7 @@ A tabela a seguir mostra quais funções do conjunto de ferramentas estão dispo
 
 Configura um parâmetro de saída da ação.
 
-Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
+Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)".
 
 ### Exemplo
 
@@ -314,7 +314,9 @@ Durante a execução de um fluxo de trabalho, o executor gera arquivos temporár
 
 {% warning %}
 
-**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão. Certifique-se de escrever os arquivos usando a codificação correta. Por exemplo, você deve definir a codificação UTF-8 ao definir o caminho:
+**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão.
+
+When using `shell: powershell`, you must specify UTF-8 encoding. Por exemplo:
 
 ```yaml
 jobs:
@@ -325,22 +327,7 @@ jobs:
         run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
 ```
 
-Ou mude para PowerShell Core, cujo padrão é UTF-8:
-
-```yaml
-jobs:
-  modern-pwsh-example:
-    uses: windows-2019
-    steps:
-      - shell: pwsh
-        run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8
-```
-
-Mais detalhes sobre UTF-8 e PowerShell Core encontrados nesta excelente [resposta do Stack Overflow](https://stackoverflow.com/a/40098904/162694):
-
-> ### Leitura opcional: A perspectiva entre plataformas: PowerShell _Core_:
-> 
-> [O PowerShell agora é multiplataforma](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), por meio da sua edição do **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)**, cuja codificação - sensívelmente - *** é igual a ***BOM-less UTF-8******, em linha com plataformas do Unix.
+Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8.
 
 {% endwarning %}
 
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index dcdea0f192..a8337f8e28 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -757,6 +757,8 @@ strategy:
 
 ## `jobs.<job_id>.container`
 
+{% data reusables.github-actions.docker-container-os-support %}
+
 {% data reusables.actions.jobs.section-running-jobs-in-a-container %}
 
 ### `jobs.<job_id>.container.image`
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index c441c63d2a..fc92d11de1 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -700,7 +700,7 @@ Todos os testes de armazenamento aprovados
 
 O `ghe-migrator` é uma ferramenta de alta fidelidade que ajuda a fazer migrações de uma instância do GitHub para outra. Você pode consolidar suas instâncias ou mover a organização, os usuários, as equipes e os repositórios do GitHub.com para o {% data variables.product.prodname_enterprise %}.
 
-Para obter mais informações, consulte nosso guia sobre [como migrar dados de usuário, organização e repositório](/enterprise/admin/guides/migrations/).
+Para obter mais informações, consulte nossos guias sobre [migração de dados para a sua empresa](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/).
 
 ### git-import-detect
 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 8d7334316d..36f66620c8 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -137,5 +137,5 @@ $ ghe-restore -c 169.154.1.1
 {% endnote %}
 
 Você pode usar estas opções adicionais com o comando `ghe-restore`:
-- O sinalizador `-c` substitui as configurações, os certificados e os dados de licença no host de destino, mesmo que já configurado. Omita esse sinalizador se você estiver configurando uma instância de preparo para fins de teste e se quiser manter a configuração no destino. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- O sinalizador `-c` substitui as configurações, os certificados e os dados de licença no host de destino, mesmo que já configurado. Omita esse sinalizador se você estiver configurando uma instância de preparo para fins de teste e se quiser manter a configuração no destino. Para obter mais informações, consulte a seção "Usando comandos de backup e restauração" do [LEIAME do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
 - O sinalizador `-s` permite selecionar outro instantâneo de backup.
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
index 94bba161d9..eac0bd8371 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
@@ -35,7 +35,7 @@ Tanto a alta disponibilidade (High Availability, HA) quanto o cluster fornecem r
 
 ## Backups e recuperação de desastre
 
-Neither HA nor Clustering should be considered a replacement for regular backups. Para obter mais informações, consulte "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)".
+Nem o clustering nem a HA devem ser considerados como substitutos para as medidas regulares de backup. Para obter mais informações, consulte "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)".
 
 ## Monitoramento
 
diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index 6cda083d1e..e90307d494 100644
--- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -52,11 +52,11 @@ Se você usa ações do contêiner do Docker ou contêineres de serviço nos seu
 
 Se estas configurações não estiverem definidas corretamente, você poderá receber erros como `Recurso movido inesperadamente para https://<IP_ADDRESS>` ao definir ou mudar a configuração de {% data variables.product.prodname_actions %}.
 
-## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
+## Os executores não se conectam a {% data variables.product.prodname_ghe_server %} com um novo nome de host
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
+Se você implantar {% data variables.product.prodname_ghe_server %} no seu ambiente com um novo nome de host e o antigo nome de host não resolver mais a sua instância, os executores auto-hospedados não conseguirão conectar-se ao nome de host antigo e não executarão nenhum trabalho.
 
 Você precisará atualizar a configuração dos seus executores auto-hospedados para usar o novo nome de host para {% data variables.product.product_location %}. Cada executor auto-hospedado exigirá um dos seguintes procedimentos:
 
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index 24633faf3d..d565787706 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -1,7 +1,7 @@
 ---
-title: About GitHub Actions for enterprises
+title: Sobre o GitHub Actions para empresas
 shortTitle: Sobre ações do GitHub
-intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
+intro: '{% data variables.product.prodname_actions %} pode melhorar a produtividade do desenvolvedor automatizando o ciclo de desenvolvimento de software da sua empresa.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -12,31 +12,31 @@ topics:
   - Enterprise
 ---
 
-With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
+Com {% data variables.product.prodname_actions %}, você pode melhorar a produtividade do desenvolvedor automatizando todas as fases do fluxo de trabalho de desenvolvimento de software da sua empresa.
 
-| Tarefa                                                                | Mais informações                                                                                                                                                       |
-| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Automatically test and build your application                         | [Sobre integração contínua](/actions/automating-builds-and-tests/about-continuous-integration)                                                                         |
-| Deploy your application                                               | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)"                                                                     |
-| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)"                               |
-| Automate your project management tasks                                | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
+| Tarefa                                                                      | Mais informações                                                                                                                                                               |
+| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Testar e compilar automaticamente o seu aplicativo                          | [Sobre integração contínua](/actions/automating-builds-and-tests/about-continuous-integration)                                                                                 |
+| Implantar seu aplicativo                                                    | "[Sobre a implantação contínua](/actions/deployment/about-deployments/about-continuous-deployment)"                                                                            |
+| Empacotar código automaticamente e com segurança em artefatos e contêineres | "[Sobre empacotamento com {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)"                                    |
+| Automatize suas tarefas de gerenciamento de projetos                        | "[Usando {% data variables.product.prodname_actions %} para gerenciamento de projeto](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
 
-{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
+{% data variables.product.prodname_actions %} ajuda a sua equipe a trabalhar mais rápido e em escala. Quando grandes repositórios começam a usar o {% data variables.product.prodname_actions %}, as equipes fazem merge de um número significativamente maior de pull requests por dia, e os pull requests são mesclados muito mais rapidamente. Para obter mais informações, consulte "[Gravação e envio mais rápido de código](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" no estado do Octoverse.
 
-{% data variables.product.prodname_actions %} also provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+{% data variables.product.prodname_actions %} também fornece maior controle sobre implantações. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir ou restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos.{% ifversion ghec or ghae-issue-4856 %} Se os seus fluxos de trabalho precisarem acessar recursos de um provedor de nuvem compatível com o OpenID Connect (OIDC), você poderá configurar seus fluxos de trabalho para efetuar a autenticação diretamente no provedor de nuvem. Isso permitirá que você pare de armazenar credenciais como segredos de longa duração e irá fornecer outros benefícios de segurança. Para obter mais informações, consulte[Sobre segurança fortalecida com OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
 
-{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
+{% data variables.product.prodname_actions %} é intuitivo para o desenvolvedor, pois está integrado diretamente à experiência familiar de {% data variables.product.product_name %}.
 
-You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. Para obter mais informações, consulte "[Localizar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)".
+Você pode criar suas próprias automações exclusivas ou você pode usar e adaptar os fluxos de trabalho do nosso ecossistema de mais de 10, 00 ações construídas por líderes do setor e pela comunidade de código aberto. Para obter mais informações, consulte "[Localizar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)".
 
-{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% ifversion ghec %}Você pode desfrutar da conveniência de executores hospedados em {% data variables.product.company_short %}, que são mantidos e atualizados por {% data variables.product.company_short %} ou você{% else %}{% endif %} pode controlar a sua própria infraestrutura privada de CI/CD usando executores auto-hospedados. Os executores auto-hospedados permitem que você determine o ambiente exato e os recursos que completam suas compilações, testes e implantações sem expor o seu ciclo de desenvolvimento de software à internet. Para obter mais informações, consulte {% ifversion ghec %}"[Sobre executores auto-hospedados em {% data variables.product.company_short %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e {% endif %} "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 
-{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
+{% data variables.product.prodname_actions %} também inclui ferramentas para governar o ciclo de desenvolvimento de software da sua empresa e atender às obrigações de conformidade. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
 
 
-To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
+Para saber mais sobre como você pode fazer a adoção de {% data variables.product.prodname_actions %} com sucesso para sua empresa, siga o caminho de aprendizado "[Adotando {% data variables.product.prodname_actions %} para a sua empresa](/admin/guides#adopt-github-actions-for-your-enterprise)".
 
 ## Leia mais
 
-- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
-- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
+- "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
+- "[Sobre a cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 9ddb86cb63..0d82557bc7 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -14,7 +14,7 @@ topics:
 
 ## Sobre {% data variables.product.prodname_actions %} para empresas
 
-{% data reusables.actions.about-actions %} com {% data variables.product.prodname_actions %}, sua empresa pode automatizar, personalizar e executar seus fluxos de trabalho de desenvolvimento de software como testes e implantações. For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
+{% data reusables.actions.about-actions %} com {% data variables.product.prodname_actions %}, sua empresa pode automatizar, personalizar e executar seus fluxos de trabalho de desenvolvimento de software como testes e implantações. Para obter mais informações, consulte a seção "[Sobre o {% data variables.product.prodname_actions %} para empresas ](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)".
 
 ![Diagrama de trabalhos em execução em executores auto-hospedados](/assets/images/help/images/actions-enterprise-overview.png)
 
diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 5ca5675755..993c9e95cd 100644
--- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -47,7 +47,7 @@ Nós testamos e oferecemos compatibilidade oficial os seguintes IdPs. Para o SSO
 | -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
 | Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
 | Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
-| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | OneLogin                                     | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | PingOne                                      | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | Shibboleth                                   | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
diff --git a/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
index 94a59a4a6f..d666cf4502 100644
--- a/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing compliance reports for your enterprise
-intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
+title: Acessando relatórios de conformidade para a sua empresa
+intro: 'Você pode acessar as denúncias de conformidade de {% data variables.product.company_short %}, como nossos relatórios SOC e auto-avaliação da Cloud Security Alliance CAIQ (CSA CAIQ), para a sua empresa.'
 versions:
   ghec: '*'
 type: how_to
@@ -9,23 +9,23 @@ topics:
   - Enterprise
   - Fundamentals
 permissions: Enterprise owners can access compliance reports for the enterprise.
-shortTitle: Access compliance reports
+shortTitle: Acessar relatórios de conformidade
 ---
 
-## About {% data variables.product.company_short %}'s compliance reports
+## Sobre os relatórios de conformidade de {% data variables.product.company_short %}
 
-You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
+Você pode acessar os relatórios de conformidade de {% data variables.product.company_short %} nas configurações da empresa.
 
 {% data reusables.security.compliance-report-list %}
 
-## Accessing compliance reports for your enterprise
+## Acessando relatórios de conformidade para a sua empresa
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
-1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+1. Em "Resources", à direita do relatório que você deseja acessar, clique em {% octicon "download" aria-label="The Download icon" %} **Download** ou {% octicon "link-external" aria-label="The external link icon" %} **Visualizar**.
 
    {% data reusables.security.compliance-report-screenshot %}
 
 ## Leia mais
 
-- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+- "[Acessando os relatórios de conformidade para a sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index dadae44d60..576432e201 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -100,7 +100,7 @@ Você pode aplicar políticas para controlar como {% data variables.product.prod
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
+Se uma política for habilitada para uma empresa, ela poderá ser desabilitada seletivamente em organizações individuais ou repositórios. Se uma política estiver desabilitada para uma empresa, as organizações individuais ou repositórios não poderão habilitá-la.
 
 {% data reusables.github-actions.private-repository-forks-options %}
 
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 75aaf2ce9f..cebec74733 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -148,6 +148,6 @@ A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no
 {% ifversion ghec or ghae %}
 ## Leia mais
 
-- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
-- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
+- "[Sobre a identidade e gerenciamento de acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
+- "[Relatórios de conformidade para a sua empresa](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
 {% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
index b9ee2bf230..68c26a6660 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
@@ -99,7 +99,7 @@ shortTitle: Exportar da sua empresa
   > logout
   > Connection to <em>hostname</em> closed.
   ```
-9. Copie o arquivo de migração para o seu computador usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp). O arquivo terá o nome do GUID de Migração:
+9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. O arquivo terá o nome do GUID de Migração:
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:/data/github/current/tmp/<em>MIGRATION_GUID</em>.tar.gz ~/Desktop
   ```
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index 3d5fefbed1..12d9cca47a 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -20,7 +20,7 @@ shortTitle: Prepare-se para fazer a migração dos dados
 
 ## Preparar os dados migrados para importação para {% data variables.product.prodname_ghe_server %}
 
-1. Usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie o arquivo de migração gerado na organização ou instância de origem para o destino no {% data variables.product.prodname_ghe_server %}:
+1. Usando o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp), copie o arquivo de migração gerado na organização ou instância de origem para o destino no {% data variables.product.prodname_ghe_server %}:
 
     ```shell
     $ scp -P 122 <em>/path/to/archive/MIGRATION_GUID.tar.gz</em> admin@<em>hostname</em>:/home/admin/
@@ -44,7 +44,7 @@ shortTitle: Prepare-se para fazer a migração dos dados
     $ ghe-migrator conflicts -g <em>MIGRATION_GUID</em> > conflicts.csv
     ```
     - Se nenhum conflito for relatado, você poderá importar os dados com segurança seguindo as etapas em "[Migrar dados para a sua empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
-2. Se houver conflitos, usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie *conflicts.csv* para o seu computador local:
+2. Se houver conflitos, usando o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp), copie *conflicts.csv* para o seu computador local:
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:conflicts.csv ~/Desktop
   ```
@@ -134,7 +134,7 @@ O mesmo processo pode ser usado para criar mapeamentos em cada registro compatí
 
 ### Aplicar dados de migração modificados
 
-1. Depois de fazer as alterações, use o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) para aplicar o seu *conflicts.csv* modificado (ou qualquer outro arquivo de mapeamento *.csv* no formato correto) para a instância de destino:
+1. Depois de fazer as alterações, use o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) para aplicar o seu *conflicts.csv* modificado (ou qualquer outro arquivo de mapeamento *.csv* no formato correto) para a instância de destino:
 
     ```shell
     $ scp -P 122 ~/Desktop/conflicts.csv admin@<em>hostname</em>:/home/admin/
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
index 417370582f..8b03a3ef80 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
@@ -29,7 +29,7 @@ Você pode recuperar uma lista de endereços IP do {% data variables.product.pro
 
 Esses endereços IP são usados por {% data variables.product.prodname_dotcom %} para fornecer nosso conteúdo, webhooks e executar compilações de {% data variables.product.prodname_actions %} hospedadas.
 
-Esses intervalos estão na [notação CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). É possível usar uma ferramenta de conversão online, como essa [Calculadora Supernet CIDR/VLSM](http://www.subnet-calculator.com/cidr.php), para fazer a conversão de notação CIDR em intervalos de endereços IP.
+Esses intervalos estão na [notação CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool to convert from CIDR notation to IP address ranges, for example: [CIDR to IPv4 conversion site](https://www.ipaddressguide.com/cidr).
 
 Nós alteramos nossos endereços IP de vez em quando. Não recomendamos permitir por endereço IP. No entanto, se você usar esses intervalos de IP, é altamente recomendável o monitoramento regular da nossa API.
 
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index 1da8ac4c25..24a48ffcd1 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,8 +18,8 @@ shortTitle: Chaves de implantação
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
-3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
+3. Na seção "Segurança" na barra lateral, clique em **{% octicon "key" aria-label="The key icon" %} Implantar chaves**.
 {% else %}
 3. Na barra lateral esquerda, clique em **Deploy keys** (Chaves de implantação). ![Configuração das chaves de implantação](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
 {% endif %}
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 4e8b030f51..f0019c2183 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -22,8 +22,8 @@ shortTitle: Log de segurança
 O log de segurança lista todas as ações realizadas nos últimos 90 dias.
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
-1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
+1. Na seção "Arquivos" da barra lateral, clique em **Registro de segurança de {% octicon "log" aria-label="The log icon" %}**.
 {% else %}
 1. Na barra lateral de configurações do usuário, clique em **log de segurança**. ![Aba do log de segurança](/assets/images/help/settings/audit-log-tab.png)
 {% endif %}
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index 485706716c..b230ae40d3 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -24,7 +24,7 @@ shortTitle: Atualizar credenciais de acesso
 1. Para solicitar uma nova senha, acesse {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
 2. Insira o endereço de e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e, em seguida, clique em **em Enviar e-mail de redefinição de senha.** O e-mail será enviado para o endereço de e-mail de backup, se você tiver um configurado. ![Caixa de diálogo para solicitar e-mail de redefinição de senha](/assets/images/help/settings/password-recovery-email-request.png)
 3. Nós enviaremos por e-mail um link para você redefinir sua senha. Clique nele em até 3 horas após o recebimento do e-mail. Se você não receber o e-mail com o link, verifique sua pasta de spam.
-4. Se você tiver habilitado a autenticação de dois fatores, será solicitado que você crie suas credenciais de 2FA. Digite as suas credenciais de 2FA ou um de seus códigos de recuperação de 2FA e clique em **Verificar**. ![Instrução de autenticação de dois fatores](/assets/images/help/2fa/2fa-password-reset.png)
+4. Se você tiver habilitado a autenticação de dois fatores, será solicitado que você crie suas credenciais de 2FA. Digite o seu código de autenticação ou um dos seus códigos de recuperação e clique em **Verificar**. Se você adicionou uma chave de segurança à sua conta, você pode inserir a chave e clicar em **Usar a chave de segurança** ao invés de digitar um código de autenticação. ![Instrução de autenticação de dois fatores](/assets/images/help/2fa/2fa-password-reset.png)
 5. Digite uma nova senha, confirme a sua nova senha e clique em **Alterar senha**. Para ajudar a criar uma senha forte, consulte "[Criar uma senha forte](/articles/creating-a-strong-password)".
   {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
   ![Caixa para recuperar senha](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 4fac2ddf2f..30eb1ff3ad 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -36,13 +36,13 @@ Use um dos códigos de recuperação para obter acesso automaticamente à sua co
 {% data reusables.two_fa.username-password %}
 
 {% ifversion fpt or ghec %}
-1. Under "Having problems?", click **Use a recovery code or request a reset**.
+1. Em "Encontrou algum problema?", clique em **Use um código de recuperação ou solicite a redefinição**.
 
-   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png)
+   ![Captura de tela do link para usar um código de recuperação](/assets/images/help/2fa/2fa-recovery-code-link.png)
 {%- else %}
 1. Na página da 2FA, em "Don't have your phone?" (Não está com seu telefone?), clique em **Enter a two-factor recovery code** (Digite um código de recuperação de dois fatores).
 
-   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+   ![Captura de tela do link para usar um código de recuperação](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
 1. Digite um dos seus códigos de recuperação e clique em **Verify** (Verificar).
 
    ![Campo para digitar um código de recuperação e botão Verify (Verificar)](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
@@ -60,11 +60,11 @@ Se você configurou a autenticação de dois fatores com uma chave de segurança
 {% ifversion fpt or ghec %}
 ## Efetuar a autenticação com um dispositivo verificado, token SSH ou token de acesso pessoal
 
-If you know your password for {% data variables.product.product_location %} but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+Se você souber a sua senha para {% data variables.product.product_location %}, mas não tiver credenciais de autenticação de dois fatores ou seus códigos de recuperação de autenticação em de dois fatores, você poderá receber por e-mail uma senha única para começar o processo de verificação e recuperar o acesso à sua conta.
 
 {% note %}
 
-**Observação**: Por razões de segurança, recuperar o acesso à sua conta efetuando a autenticação com uma senha única pode levar de 1 a 3 dias úteis. {% data variables.product.company_short %} will not review additional requests submitted during this time.
+**Observação**: Por razões de segurança, a recuperação do acesso à sua conta efetuando a autenticação com uma senha única pode levar até três dias úteis. {% data variables.product.company_short %} não analisará solicitações adicionais enviadas nesse tempo.
 
 {% endnote %}
 
@@ -77,30 +77,30 @@ Você pode usar as suas credenciais de autenticação de dois fatores ou os cód
     **Aviso**: {% data reusables.accounts.you-must-know-your-password %}
 
     {% endwarning %}
-1. Under "Having problems?", click **Use a recovery code or request a reset**.
+1. Em "Encontrou algum problema?", clique em **Use um código de recuperação ou solicite a redefinição**.
 
-   ![Screenshot of link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
-1. To the right of "Locked out?", click **Try recovering your account**.
+   ![Captura de tela do link se você não tiver seu dispositivo 2FA ou códigos de recuperação](/assets/images/help/2fa/no-access-link.png)
+1. À direita de "Bloqueado?", clique em **Tente recuperar sua conta**.
 
-   ![Screenshot of link to try recovering your account](/assets/images/help/2fa/try-recovering-your-account-link.png)
+   ![Captura de tela do link para tentar recuperar sua conta](/assets/images/help/2fa/try-recovering-your-account-link.png)
 1. Clique em **Eu entendo, começar** para solicitar uma redefinição das suas configurações de autenticação.
 
-    ![Screenshot of button to start reset of authentication settings](/assets/images/help/2fa/reset-auth-settings.png)
-1. Click **Send one-time password** to send a one-time password to all eligible addresses associated with your account. Only verified emails are eligible for account recovery. If you've restricted password resets to your primary and/or backup addresses, these addresses are the only addresses eligible for account recovery.
+    ![Captura de tela do botão para iniciar a redefinição das configurações de autenticação](/assets/images/help/2fa/reset-auth-settings.png)
+1. Clique em **Enviar senha de uso único** para enviar uma senha de uso único para todos os endereços de e-mail elegível associados à sua conta. Apenas e-mails verificados são elegíveis para a recuperação de conta. Se você restringiu as redefinições de senha para seus endereços primários e/ou de backup, esses endereços são os únicos elegíveis para a recuperação de conta.
 
-   ![Screenshot of button to send one-time password](/assets/images/help/2fa/send-one-time-password.png)
+   ![Captura de tela do botão para enviar uma senha única](/assets/images/help/2fa/send-one-time-password.png)
 1. Em "Única senha", digite a senha temporária do endereço e-mail de recuperação {% data variables.product.prodname_dotcom %} enviada.
 
-   ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png)
+   ![Captura de tela do campo para digitar senha única](/assets/images/help/2fa/one-time-password-field.png)
 1. Clique **Verificar endereço de e-mail**.
 
-   ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png)
+   ![Captura de tela do botão para verificar o endereço de e-mail](/assets/images/help/2fa/verify-email-address.png)
 1. Escolha um fator de verificação alternativo.
     - Se você usou seu dispositivo atual para acessar essa conta antes e gostaria de usar o dispositivo para verificação, clique em **Verificar com este dispositivo**.
     - Se você já configurou uma chave SSH nesta conta e gostaria de usar a chave SSH para verificação, clique na **chave SSH**.
     - Se você já configurou um token de acesso pessoal anteriormente e gostaria de usar o token de acesso pessoal para verificação, clique em **Token de acesso pessoal**.
 
-   ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png)
-1. Um integrante do {% data variables.contact.github_support %} irá rever a sua solicitação e o seu endereço de e-mail de 1 a 3 dias úteis. Se a sua solicitação for aprovada, você receberá um link para concluir o processo de recuperação de conta. Se sua solicitação for negada, o e-mail incluirá uma forma de entrar em contato com o suporte para esclarecer outras dúvidas.
+   ![Captura de tela de botões para verificação alternativa](/assets/images/help/2fa/alt-verifications.png)
+1. Um integrante de {% data variables.contact.github_support %} irá revisar a sua solicitação e enviar um e-mail para você em três dias úteis. Se a sua solicitação for aprovada, você receberá um link para concluir o processo de recuperação de conta. Se sua solicitação for negada, o e-mail incluirá uma forma de entrar em contato com o suporte para esclarecer outras dúvidas.
 
 {% endif %}
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index f4a565e01c..4c757040af 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -76,7 +76,7 @@ No final do mês, {% data variables.product.prodname_dotcom %} calcula o custo d
 
 ### Cálculo de custo de amostra em minutos
 
-Por exemplo, se sua organização usa {% data variables.product.prodname_team %} e permite gastos ilimitados, usando 15.000 minutos, poderia ter um custo total de armazenamento e custo médio de minuto de US$ 56,00, dependendo dos sistemas operacionais usados para executar trabalhos.
+For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
 
 - 5.000 (3.000 Linux e 2.000 Windows) minutos = US$ 56 (US$ 24 + US$ 32).
   - 3.000 minutos de Linux por US$ 0,008 por minuto = US$ 24.
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index 351e6baf57..0cb030856c 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -54,10 +54,12 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim
 {% data reusables.codespaces.exporting-changes %}
 ## Gerenciamento de notificações por e-mail e limite de gastos
 
-As notificações de e-mail são enviadas para os proprietários de contas e gerentes de cobrança quando os gastos chegam a 50%, 75% e 90% do limite de gastos da sua conta.
+Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
 
 Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**.
 
+![Screenshot of the billing email notification settings](/assets/images/help/billing/codespaces-spending-limit-notifications.png)
+
 ## Leia mais
 
 - "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index c5bbaac064..3239198ecc 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -48,7 +48,7 @@ Por padrão, a página de verificação de código de alertas é filtrada para m
 1. Opcionalmente, se o alerta destacar um problema com o fluxo de dados, clique em **Mostrar caminhos** para exibir o caminho da fonte de dados até o destino onde é usado. ![O link "Exibir caminhos" em um alerta](/assets/images/help/repository/code-scanning-show-paths.png)
 1. Alertas da análise de {% data variables.product.prodname_codeql %} incluem uma descrição do problema. Clique em **Mostrar mais** para obter orientação sobre como corrigir seu código. ![Detalhes para um alerta](/assets/images/help/repository/code-scanning-alert-details.png)
 
-For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
+Para obter mais informações, consulte "[Sobre alertas de {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% note %}
@@ -77,7 +77,7 @@ Se você inserir vários filtros, a visualização mostrará alertas que corresp
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 
-Você pode prefixar o filtro `tag` com `-` para excluir resultados com essa tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% if codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
+Você pode prefixar o filtro `tag` com `-` para excluir resultados com essa tag. Por exemplo, `-tag:style` mostra apenas alertas que não têm a tag `estilo`{% if codeql-ml-queries %} e `-tag:experimental` omitirá todos os alertas experimentais. Para obter mais informações, consulte "[Sobre alertas de{% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
 
 {% endif %}
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 4271ef318a..aaeaf6d618 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -188,16 +188,16 @@ Se você dividir sua análise em vários fluxos de trabalho, conforme descrito a
 
 <p spaces-before="0">Se sua análise ainda é muito lenta para ser executada durante eventos <code>push` ou `pull_request`, você poderá acionar apenas a análise no evento `agendamento`. Para obter mais informações, consulte "[Eventos](/actions/learn-github-actions/introduction-to-github-actions#events)".</p>
 
-### Check which query suites the workflow runs
+### Verifique qual conjunto de consultas que o fluxo de trabalho executa
 
-By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
+Por padrão, existem três principais conjuntos de consultas disponíveis para cada linguagem. Se você otimizar a compilação do banco de dados CodeQL mesmo assim o processo continuar sendo muito longo, você poderá reduzir o número de consultas que você executa. O conjunto de consulta padrão é executado automaticamente. Ele contém as consultas de segurança mais rápidas com as taxas mais baixas de resultados falso-positivos.
 
-You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+Você pode executar consultas adicionais ou conjuntos de consulta além das consultas padrão. Verifique se o fluxo de trabalho define um conjunto de consultas adicional ou consultas adicionais a serem executadas usando o elemento `consultas`. Você pode experimentar desabilitar o conjunto de consultas adicionais ou consultas. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
 
 {% if codeql-ml-queries %}
 {% note %}
 
-**Note:** If you run the `security-extended` or `security-and-quality` query suite for JavaScript, then some queries use experimental technology. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."
+**Observação:** Se você executar `security-extended` ou a consulta `security-and-quality` para o JavaScript, algumas consultas irão usar a tecnologia experimental. Para obter mais informações, consulte "[Sobre a alertas da digitalização de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)".
 {% endnote %}
 {% endif %}
 
@@ -216,7 +216,7 @@ Se a execução de um fluxo de trabalho para {% data variables.product.prodname_
 
 ## Erro: "Fora do disco" ou "Sem memória"
 
-On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
+Em projetos muito grandes, {% data variables.product.prodname_codeql %} pode ficar ficar sem disco ou sem memória no executor.
 {% ifversion fpt or ghec %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema.
 {% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %}
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
index 482b8eacf8..2c94bf189c 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -325,7 +325,7 @@ codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
     </td>
     
     <td>
-      Especifique pacotes ou consultas de {% data variables.product.prodname_codeql %} para executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, omita este parâmetro. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in <code>/&lt;extraction-root&gt;/qlpacks/codeql/&lt;language&gt;-queries/codeql-suites</code>. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Criando conjuntos de consultas de CodeQL</a> na documentação do {% data variables.product.prodname_codeql_cli %}.
+      Especifique pacotes ou consultas de {% data variables.product.prodname_codeql %} para executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, omita este parâmetro. Para ver os outros itens de consulta incluídos no pacote de {% data variables.product.prodname_codeql_cli %}, consulte <code>/&lt;extraction-root&gt;/qlpacks/codeql/&lt;language&gt;-queries/codeql-suites</code>. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Criando conjuntos de consultas de CodeQL</a> na documentação do {% data variables.product.prodname_codeql_cli %}.
     </td>
   </tr>
   
diff --git a/translations/pt-BR/content/code-security/getting-started/github-security-features.md b/translations/pt-BR/content/code-security/getting-started/github-security-features.md
index 450bb7ac3a..38d92740a4 100644
--- a/translations/pt-BR/content/code-security/getting-started/github-security-features.md
+++ b/translations/pt-BR/content/code-security/getting-started/github-security-features.md
@@ -86,7 +86,7 @@ Mostre o impacto completo das alterações nas dependências e veja detalhes de
 {% ifversion ghec or ghes > 3.1 %}
 ### Visão geral da segurança
 
-Review the security configuration and alerts for your organization and identify the repositories at greatest risk. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".
+Revise a configuração de segurança e os alertas para sua organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".
 {% endif %}
 
 ## Leia mais
diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
index 25e29b59c1..06b8cdd44e 100644
--- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
@@ -36,7 +36,7 @@ Você pode criar uma política de segurança padrão que será exibida em qualqu
 {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %}
 ## Gerenciar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências
 
-{% ifversion fpt or ghec %}Por padrão, {% data variables.product.prodname_dotcom %} detecta vulnerabilidades nos repositórios públicos, gera {% data variables.product.prodname_dependabot_alerts %} e um gráfico de dependência. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta vulnerabilidades em repositórios públicos e exibe o gráfico de dependências. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios públicos pertencentes à sua organização. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização.
 
 1. Clique na sua foto de perfil e clique em **Organizações**.
 2. Clique em **Configurações** ao lado da sua organização.
@@ -143,5 +143,5 @@ Você pode visualizar e gerenciar alertas de funcionalidades de segurança para
 {% ifversion ghec %}
 ## Leia mais
 
-"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+"[Acessando os relatórios de conformidade para a sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 7917dc4cd7..75a95e8698 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -67,7 +67,13 @@ Antes de definir um padrão personalizado, você deve garantir que {% data varia
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
-{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}
+1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**.
+1. When the dry run finishes, you'll see a sample of results (up to 1000) from the repository. Review the results and identify any false positive results. ![Screenshot showing results from dry run](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. Edit the new custom pattern to fix any problems with the results, then click **Save and dry run** to test your changes.
+{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
+{% endif %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 Após a criação do seu padrão, {% data reusables.secret-scanning.secret-scanning-process %} Para mais informações sobre visualização de alertas {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
 
@@ -116,6 +122,7 @@ Antes de definir um padrão personalizado, você deverá habilitar {% data varia
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 Depois que o padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar todos os segredos nos repositórios {% ifversion fpt or ghec %}privados {% endif %} na sua organização, incluindo todo seu histórico do Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
 
@@ -139,6 +146,7 @@ Antes de definir um padrão personalizado, você deverá garantir que você habi
 {% data reusables.enterprise-accounts.advanced-security-security-features %}
 1. Em "Padrões de personalização de digitalização de segredos", clique em {% ifversion ghes = 3.2 %}**Novo padrão personalizado**{% else %}**Novo padrão**{% endif %}.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 Depois que seu padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar se há segredos em repositórios {% ifversion fpt or ghec %}privados{% endif %} dentro das organizações da sua empresa com {% data variables.product.prodname_GH_advanced_security %} habilitado, incluindo toda a sua história de Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
 
diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
index d9c8ee72aa..a8bc817e18 100644
--- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
@@ -28,7 +28,7 @@ shortTitle: Sobre a visão geral de segurança
 
 Você pode usar a visão geral de segurança para uma visão de alto nível do status de segurança da sua organização ou para identificar repositórios problemáticos que exigem intervenção.
 
-- A nível da organização, a visão geral de segurança exibe informações de segurança agregadas e específicas para repositórios pertencentes à sua organização. You can also filter information per security feature.
+- A nível da organização, a visão geral de segurança exibe informações de segurança agregadas e específicas para repositórios pertencentes à sua organização. Você também pode filtrar as informações por recurso de segurança.
 - No nível da equipe, a visão geral de segurança exibe informações de segurança específicas para repositórios para os quais a equipe tem privilégios de administrador. Para obter mais informações, consulte "[Gerenciando o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
 - No nível do repositório, a visão geral de segurança mostra quais recursos de segurança são habilitados para o repositório e oferece a opção de configurar todos os recursos de segurança disponíveis que não estejam em uso atualmente.
 
diff --git a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md
index c47d8c895c..6c360c7fe2 100644
--- a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md
+++ b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md
@@ -27,7 +27,7 @@ shortTitle: Ver visão geral de segurança
 1. Para visualizar informações agregadas sobre tipos de alertas, clique em **Mostrar mais**. ![Botão mostrar mais](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
 {% if security-overview-views %}
-1. Alternatively and optionally, use the sidebar on the left to filter information per security feature. On each page, you can use filters that are specific to each feature to fine-tune your search. ![Screenshot of the code scanning-specific page](/assets/images/help/organizations/security-overview-code-scanning-alerts.png)
+1. Como alternativa, use a barra lateral à esquerda para filtrar informações por recurso de segurança. Em cada página, é possível usar filtros específicos para cada recurso para ajustar sua pesquisa. ![Captura de tela da página de digitalização específica do código](/assets/images/help/organizations/security-overview-code-scanning-alerts.png)
 
 ## Visualizando alertas em toda a sua organização
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index 7df78c8222..3347986c1d 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -16,7 +16,7 @@ topics:
   - Repositories
   - Dependencies
   - Pull requests
-shortTitle: Use Dependabot with Actions
+shortTitle: Use o Dependabot com ações
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
@@ -30,11 +30,17 @@ shortTitle: Use Dependabot with Actions
 
 {% data variables.product.prodname_dependabot %} consegue acionar fluxos de trabalho de {% data variables.product.prodname_actions %} nos seus pull requests e comentários. No entanto, certos eventos são tratados de maneira diferente.
 
-Para fluxos de trabalho iniciados por eventos de {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment` e `push`, aplicam-se as restrições a seguir:
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %}
+Para fluxos de trabalho iniciados por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) que usam eventos de `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status`, aplicam-se as restrições a seguir:
+{% endif %}
 
 - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` tem permissões somente leitura, a menos que seu administrador tenha removido as restrições.{% else %}`GITHUB_TOKEN` tem permissões somente leitura por padrão.{% endif %}
 - {% ifversion ghes = 3.3 %}Os segredos são inacessíveis, a menos que o seu administrador tenha removido restrições.{% else %}Os segredos são preenchidos a partir dos segredos de {% data variables.product.prodname_dependabot %}. Os segredos de {% data variables.product.prodname_actions %} não estão disponíveis.{% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %}
+Para fluxos de trabalho iniciados por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) que usam eventos de `pull_request_target`, se a referência da base do pull request foi criada por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` será somente leitura e os segredos não estarão disponíveis.
+{% endif %}
+
 Para obter mais informações, consulte ["Manter seus GitHub Actions e fluxos de trabalho seguro: Evitando solicitações de pwn"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
index e6afe728c3..741b68509d 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
@@ -27,9 +27,9 @@ shortTitle: Opções de configuração
 
 O arquivo de configuração do {% data variables.product.prodname_dependabot %} , *dependabot.yml*, usa a sintaxe YAML. Se você não souber o que é YAMLe quiser saber mais, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
-Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. For more information and an example, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)."
+Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. Para obter mais informações e exemplos, consulte "[Habilitando e desabilitando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)".
 
-Quaisquer opções que também afetem as atualizações de segurança são usadas na próxima vez que um alerta de segurança acionar um pull request para uma atualização de segurança.  For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+Quaisquer opções que também afetem as atualizações de segurança são usadas na próxima vez que um alerta de segurança acionar um pull request para uma atualização de segurança.  Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
 
 O arquivo *dependabot.yml* tem duas chaves obrigatórias de nível superior: `versão`e `atualizações`. Opcionalmente, você pode incluir uma chave de `registro` de nível superior. O arquivo deve começar com a `versão: 2`.
 
@@ -491,9 +491,9 @@ updates:
 
 ### `registros`
 
-Para permitir que {% data variables.product.prodname_dependabot %} acesse um registro de pacote privado ao executar uma atualização de versão, você deverá incluir uma configuração de `registros` com a configuração de `atualizações` relevante. Pode permitir que todos os registros definidos sejam usados configurando `registros` como `"*"`. Como alternativa, você pode listar os registros que a atualização pode usar. Para isso, use o nome do registro conforme definido na seção de `registros` do arquivo _dependabot.yml_. For more information, see "[Configuration options for private registries](#configuration-options-for-private-registries)" below.
+Para permitir que {% data variables.product.prodname_dependabot %} acesse um registro de pacote privado ao executar uma atualização de versão, você deverá incluir uma configuração de `registros` com a configuração de `atualizações` relevante. Pode permitir que todos os registros definidos sejam usados configurando `registros` como `"*"`. Como alternativa, você pode listar os registros que a atualização pode usar. Para isso, use o nome do registro conforme definido na seção de `registros` do arquivo _dependabot.yml_. Para obter mais informações, consulte "[Opções de configuração para registros privados](#configuration-options-for-private-registries)" abaixo.
 
-Para permitir que {% data variables.product.prodname_dependabot %} use os gerenciadores de pacote `bundler`, `mix` e `pip` para atualizar dependências em registros privados, você pode optar por permitir a execução de código externo. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above.
+Para permitir que {% data variables.product.prodname_dependabot %} use os gerenciadores de pacote `bundler`, `mix` e `pip` para atualizar dependências em registros privados, você pode optar por permitir a execução de código externo. Para obter mais informações, consulte [`insecure-external-code-execution`](#insecure-external-code-execution) acima.
 
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 982e9cd23f..e6b09504d6 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -59,7 +59,7 @@ Para obter uma lista dos ecossistemas para os quais o {% data variables.product.
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e exibe o gráfico de dependências, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Proprietários de repositórios ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %} para repositórios públicos. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios.
 
 Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios pertencentes à sua conta de usuário ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
index b34478a84c..2fd57be3ac 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
@@ -46,8 +46,6 @@ Há três razões pelas quais um alerta pode não ter link de um pull request:
 
 Se um erro impediu que {% data variables.product.prodname_dependabot %} criasse um pull request, você pode exibir os detalhes do erro clicando no alerta.
 
-![O alerta do {% data variables.product.prodname_dependabot %} que mostra que o erro que bloqueou a criação de um pull request](/assets/images/help/dependabot/dependabot-security-update-error.png)
-
 ## Investigar erros com {% data variables.product.prodname_dependabot_version_updates %}
 
 Quando {% data variables.product.prodname_dependabot %} está impedido de criar um pull request para atualizar uma dependência em um ecossistema, ele posta o ícone de erro no arquivo de manifesto. Os arquivos de manifesto gerenciados por {% data variables.product.prodname_dependabot %} estão listados na aba {% data variables.product.prodname_dependabot %}. Para acessar essa aba, na aba **Insights** para o repositório, clique no **Gráfico de Dependências**, e, em seguida, clique na aba **{% data variables.product.prodname_dependabot %}**.
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 842cc5a243..df01ad74b9 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -103,17 +103,17 @@ Uma vez que {% data variables.product.prodname_dependabot %} usa dados curados e
 {% ifversion fpt or ghec %}
 ## Cada vulnerabilidade de dependência gera um alerta separado?
 
-Quando uma dependência tem várias vulnerabilidades, apenas um alerta agregado é gerado para essa dependência, em vez de um alerta por vulnerabilidade.
+Quando uma dependência tem várias vulnerabilidades, gera-se um alerta para cada vulnerabilidade no nível da consultoria mais manifesto.
 
-A contagem de {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.prodname_dotcom %} mostra um total para o número de alertas, ou seja, o número de dependências com vulnerabilidades, não o número de vulnerabilidades.
+![Captura de tela da aba de {% data variables.product.prodname_dependabot_alerts %} que mostra dois alertas do mesmo pacote com manifestos diferentes.](/assets/images/help/repository/dependabot-alerts-view.png)
 
-![Vista de {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-view.png)
+O legado de {% data variables.product.prodname_dependabot_alerts %} foi agrupado em um único alerta agregado com todas as vulnerabilidades para a mesma dependência. Se você acessar um link para um alerta de legadode {% data variables.product.prodname_dependabot %}, você será redirecionado para a aba de {% data variables.product.prodname_dependabot_alerts %} filtrada para exibir vulnerabilidades para esse pacote e manifesto dependente.
 
-Ao clicar para exibir os detalhes de alerta, você pode ver quantas vulnerabilidades são incluídas no alerta.
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png)
 
-![Múltiplas vulnerabilidades para um alerta de {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
+The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies.
 
-**Verifique**: Se houver discrepância no total que você está vendo, verifique se você não está comparando números de alerta com números de vulnerabilidade.
+**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
 {% endif %}
 
 ## Leia mais
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index 8c2421d757..f16fa4a212 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -25,7 +25,7 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-A aba de {% data variables.product.prodname_dependabot_alerts %} do seu repositório lista todos os {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} abertos e fechados correspondentes a {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. Você pode ordenar a lista de alertas selecionando o menu suspenso e você pode clicar em alertas específicos para obter mais detalhes. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
+Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
@@ -37,11 +37,26 @@ A aba de {% data variables.product.prodname_dependabot_alerts %} do seu reposit
 ## Sobre atualizações para dependências vulneráveis no seu repositório
 
 {% data variables.product.product_name %} gera {% data variables.product.prodname_dependabot_alerts %} quando detectamos que sua base de código está usando dependências com vulnerabilidades conhecidas. Para repositórios em que {% data variables.product.prodname_dependabot_security_updates %} estão habilitados, quando {% data variables.product.product_name %} detecta uma dependência vulnerável no branch padrão, {% data variables.product.prodname_dependabot %} cria um pull request para corrigi-la. O pull request irá atualizar a dependência para a versão minimamente segura possível, o que é necessário para evitar a vulnerabilidade.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`).
+
+Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %}
 {% endif %}
 
 ## Visualizar e atualizar dependências vulneráveis
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png)
+1. Click the alert that you would like to view. ![Alerta selecionado na lista de alertas](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png)
+1. Revise as informações da vulnerabilidade e, se disponível, o pull request que contém a atualização de segurança automatizada.
+1. Opcionalmente, se ainda não houver uma atualização de {% data variables.product.prodname_dependabot_security_updates %} para o alerta, crie um pull request para resolver a vulnerabilidade. Clique em **Criar uma atualização de segurança de {% data variables.product.prodname_dependabot %}**. ![Crie um botão de atualização de segurança do {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
+1. Quando estiver pronto para atualizar a dependência e resolver a vulnerabilidade, faça merge da pull request. Cada pull request criado por {% data variables.product.prodname_dependabot %} inclui informações sobre os comandos que você pode usar para controlar {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciar pull requests para atualizações de dependências](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)".
+1. Opcionalmente, se o alerta estiver sendo corrigido, se estiver incorreto, ou localizado em um código não utilizado, selecione o menu suspenso "Ignorar" e clique em um motivo para ignorar o alerta. ![Escolher o motivo para ignorar o alerta a partir do menu suspenso "Ignorar"down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png)
+
+{% elsif ghes = 3.3 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -51,7 +66,7 @@ A aba de {% data variables.product.prodname_dependabot_alerts %} do seu reposit
 1. Quando estiver pronto para atualizar a dependência e resolver a vulnerabilidade, faça merge da pull request. Cada pull request criado por {% data variables.product.prodname_dependabot %} inclui informações sobre os comandos que você pode usar para controlar {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciar pull requests para atualizações de dependências](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)".
 1. Opcionalmente, se o alerta estiver sendo corrigido, se estiver incorreto, ou localizado em um código não utilizado, selecione o menu suspenso "Ignorar" e clique em um motivo para ignorar o alerta. ![Escolher o motivo para ignorar o alerta a partir do menu suspenso "Ignorar"down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
-{% elsif ghes > 3.0 or ghae-issue-4864 %}
+{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 0374f432e7..e114976e99 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -38,7 +38,7 @@ A revisão de dependências está disponível quando o gráfico de dependências
 
 Às vezes, você pode apenas querer atualizar a versão de uma dependência em um manifesto e gerar um pull request. No entanto, se a versão atualizada desta dependência direta também atualizou as dependências, seu pull request pode ter mais alterações do que o esperado. A revisão de dependência para cada manifesto e arquivo de bloqueio fornece uma maneira fácil de ver o que foi alterado e se alguma das novas versões de dependências contém vulnerabilidades conhecidas.
 
-Ao verificar as revisões de dependências em um pull request e alterar todas as dependências sinalizadas como vulneráveis, você pode evitar que vulnerabilidades sejam adicionadas ao seu projeto. For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
+Ao verificar as revisões de dependências em um pull request e alterar todas as dependências sinalizadas como vulneráveis, você pode evitar que vulnerabilidades sejam adicionadas ao seu projeto. Para obter mais informações sobre como funciona a revisão de dependências, consulte "[Revisar as alterações de dependência em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)".
 
 {% data variables.product.prodname_dependabot_alerts %} encontrará vulnerabilidades que já estão nas suas dependências, mas é muito melhor evitar a introdução de possíveis problemas do que corrigir problemas em uma data posterior. Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)".
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 65a374e371..fa6b543bf6 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -90,22 +90,22 @@ Os formatos recomendados definem explicitamente quais versões são usadas para
 | Go modules | Go | `go.mod` | `go.mod` |
 {%- endif %}
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  | | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`| | Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %}
-{%- ifversion fpt or ghes > 3.3 %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %}
 | Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
 
 {% if github-actions-in-dependency-graph %}
-[1] Please note that {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)."
+[1] Observe que os fluxos de trabalho de {% data variables.product.prodname_actions %} devem estar localizados no diretório `.github/workflows/` de um repositório para serem reconhecidos como manifestos. Todas as ações ou fluxos de trabalho referenciados que usam a sintaxe `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` serão analisados como dependências. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)".
 
-[2] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+[2] Se você listar suas dependências do Python nas no arquivo `setup.py`, é possível que não possamos analisar e listar todas as dependências do seu projeto.
 
 {% else %}
-[1] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+[1] Se você listar suas dependências do Python no arquivo `setup.py`, é possível que não possamos analisar e listar todas as dependências do seu projeto.
 {% endif %}
 
 {% if github-actions-in-dependency-graph %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_actions %} workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for {% data variables.product.prodname_actions %} workflows.
+**Observação:** As dependências do fluxo de trabalho de {% data variables.product.prodname_actions %} são exibidas no gráfico de dependências para fins informativos. Os alertas de dependência não são atualmente compatíveis com os fluxos de trabalho de {% data variables.product.prodname_actions %}.
 
 {% endnote %}
 {% endif %}
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index c5a28310de..48d4b1a9c3 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -12,7 +12,7 @@ shortTitle: Registro de imagem privada
 
 ## Sobre registros de imagens privadas e {% data variables.product.prodname_codespaces %}
 
-Um registro é um espaço seguro para armazenar, gerenciar e buscar imagens privadas de contêineres. You may use one to store one or more images. Existem muitos exemplos de registros, como {% data variables.product.prodname_dotcom %} registro do contêiner, registro de contêiner do Azure ou DockerHub.
+Um registro é um espaço seguro para armazenar, gerenciar e buscar imagens privadas de contêineres. Você pode usar uma para armazenar uma ou mais imagens. Existem muitos exemplos de registros, como {% data variables.product.prodname_dotcom %} registro do contêiner, registro de contêiner do Azure ou DockerHub.
 
 O registro do contêiner de {% data variables.product.prodname_dotcom %} pode ser configurado para puxar imagens container sem precisar fornecer qualquer credencial para {% data variables.product.prodname_codespaces %}. Para outros registros de imagem, você deve criar segredos em {% data variables.product.prodname_dotcom %} para armazenar os detalhes de acesso, o que permitirá que {% data variables.product.prodname_codespaces %} acesse imagens armazenadas nesse registro.
 
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 4ea668eeb6..882dc68f3a 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -19,7 +19,7 @@ Para saber mais sobre os preços para {% data variables.product.prodname_codespa
 
 {% data reusables.codespaces.codespaces-billing %}
 
-- As an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
+- Como proprietário de uma organização ou gerente de cobrança, você pode gerenciar a cobrança de {% data variables.product.prodname_codespaces %} para a sua organização: ["Sobre cobrança para codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
 
 - Para os usuários, há um guia que explica como a cobrança funciona: ["Entendendo a cobrança para codespace"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index e848a75561..42daae7578 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -41,7 +41,7 @@ Para criar segredos para um repositório da organização, você deve ter acesso
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
+1. Na seção "Segurança" da barra lateral, selecione **Segredos de {% octicon "key-asterisk" aria-label="The key-asterisk icon" %}** e, em seguida, clique em **{% data variables.product.prodname_codespaces %}**.
 2. Na parte superior da página, clique em **Novo segredo de repositório**.
 3. Digite um nome para o seu segredo na caixa de entrada **Nome**.
 4. Insira o valor para o seu segredo.
@@ -55,7 +55,7 @@ Ao criar um segredo em uma organização, você pode usar uma política para lim
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
+1. Na seção "Segurança" da barra lateral, selecione **Segredos de {% octicon "key-asterisk" aria-label="The key-asterisk icon" %}** e, em seguida, clique em **{% data variables.product.prodname_codespaces %}**.
 2. Na parte superior da página, clique em **Novo segredo de organização**.
 3. Digite um nome para o seu segredo na caixa de entrada **Nome**.
 4. Insira o **Valor** para o seu segredo.
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index 3c63bb096d..a44a51cce1 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -47,7 +47,7 @@ Se você adicionar uma política para toda a organização, você deverá config
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policy**.
+1. Na seção "Código, planejamento e automação" da barra lateral, selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** e, em seguida, clique em **Política**.
 2. Na página "Políticas do codespace", clique em **Criar política**.
 3. Insira um nome para sua nova política.
 4. Clique **Adicionar restrição** e escolha **Tipos de máquina**.
diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
index f1f8f12a52..6ad3735102 100644
--- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
+++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -21,6 +21,8 @@ Você pode denunciar usuários que violaram Diretrizes da comunidade ou Termos d
 
 Se o conteúdo denunciado estiver ativado para um repositório público, você também poderá denunciar o conteúdo diretamente aos mantenedores do repositório.
 
+Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer).
+
 ## Denunciar um usuário
 
 {% data reusables.profile.user_profile_page_navigation %}
diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
index 026aa0ca3d..1cfe6e0dcc 100644
--- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
+++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
@@ -27,6 +27,6 @@ Você também pode bloquear usuários. Para obter mais informações, consulte "
 ## Limitar interações para sua conta de usuário
 
 {% data reusables.user_settings.access_settings %}
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
+1. Na seção "Acesso" da barra lateral, selecione **Moderação de {% octicon "report" aria-label="The report icon" %}** e, em seguida, clique em **Limites de interação**.
 {% data reusables.community.set-interaction-limit %}
   ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index a8b174d854..35f0427660 100644
--- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -33,7 +33,7 @@ Os proprietários da organização também podem bloquear os usuários por um de
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
+1. Na seção "Acesso" da barra lateral, selecione **Moderação de {% octicon "report" aria-label="The report icon" %}** e, em seguida, clique em **Limites de interação**.
 {% data reusables.community.set-interaction-limit %}
   ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index 6e24974852..29df8518cb 100644
--- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -28,7 +28,7 @@ Você também pode habilitar limitações de atividade em todos os repositórios
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
+1. Na seção "Acesso" da barra lateral, selecione **Opções de moderação de {% octicon "comment-discussion" aria-label="The comment-discussion icon" %}** e, em seguida, clique em **Limites de interação**.
 {% data reusables.community.set-interaction-limit %}
   ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
index 7df6fefda9..ee3d8db7a0 100644
--- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
+++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
@@ -1,6 +1,6 @@
 ---
 title: Common validation errors when creating issue forms
-intro: 'You may see some of these common validation errors when creating, saving, or viewing issue forms.'
+intro: 'Você pode ver alguns desses erros comuns de validação ao criar, salvar ou visualizar formulários de problemas.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -13,16 +13,16 @@ topics:
 
 ## Required top level key `name` is missing
 
-The template does not contain a `name` field, which means it is not clear what to call your issue template when giving users a list of options.
+O modelo não contém um campo `nome`, o que significa que não está claro que nome dar ao seu modelo de problema ao fornecer aos usuários uma lista de opções.
 
 ### Exemplo
 
 ```yaml
-description: "Thank you for reporting a bug!"
+descrição: "Obrigado por relatar um erro!"
 ...
 ```
 
-The error can be fixed by adding `name` as a key.
+O erro pode ser corrigido adicionando `nome` como chave.
 
 ```yaml
 name: "Bug report"
@@ -30,13 +30,13 @@ description: "Thank you for reporting a bug!"
 ...
 ```
 
-## `key` must be a string
+## a `chave` deve ser uma string
 
-This error message means that a permitted key has been provided, but its value cannot be parsed as the data type is not supported.
+Esta mensagem de erro significa que uma chave permitida foi fornecida, mas seu valor não pode ser analisado porque o tipo de dado não é compatível.
 
 ### Exemplo
 
-The `description` below is being parsed as a Boolean, but it should be a string.
+A `descrição` abaixo está sendo analisada como um booleano, mas deve ser uma string.
 
 ```yaml
 name: "Bug report"
@@ -44,7 +44,7 @@ description: true
 ...
 ```
 
-The error can be fixed by providing a string as the value. Strings may need to be wrapped in double quotes to be successfully parsed. For example, strings that contain `'` must be wrapped in double quotes.
+O erro pode ser corrigido fornecendo uma string como o valor. As strings podem ter de ser envolvidas em aspas duplas para serem analisadas com sucesso. Por exemplo, as strings que contenham `'` devem estar entre aspas duplas.
 
 ```yaml
 name: "Bug report"
@@ -52,7 +52,7 @@ description: "true"
 ...
 ```
 
-Empty strings, or strings consisting of only whitespaces, are also not permissible when the field expects a string.
+As strings vazias ou que consistem em espaços em branco também não são permitidas quando o campo espera uma string.
 
 ```yaml
 name: ""
@@ -61,7 +61,7 @@ assignees: "      "
 ...
 ```
 
-The error can be fixed by correcting the value to be a non-empty string. If the field is not required, you should delete the key-value pair.
+O erro pode ser corrigido ajustando o valor como uma string não vazia. Se o campo não for obrigatório, você deverá excluir o par chave-valor.
 
 ```yaml
 name: "Bug Report"
@@ -69,9 +69,9 @@ description: "File a bug report"
 ...
 ```
 
-## `input` is not a permitted key
+## `entrada` não é uma chave permitida
 
-An unexpected key was supplied at the top level of the template. For more information about which top-level keys are supported, see "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax)."
+Uma chave inesperada foi fornecida no nível superior do modelo. Para obter mais informações sobre quais chaves de nível superior são compatíveis, consulte "[Sintaxe para os formulários do problema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax). "
 
 ### Exemplo
 
@@ -81,24 +81,24 @@ hello: world
 ...
 ```
 
-The error can be fixed by removing the unexpected keys.
+O erro pode ser corrigido removendo as chaves inesperadas.
 
 ```yaml
 name: "Bug report"
 ...
 ```
 
-## Forbidden keys
+## Chaves proibidas
 
-YAML parses certain strings as `Boolean` values. To avoid this, we have explicitly forbidden the usage of the following keys:
+O YAML analisa certas strings como valores `booleanos`. Para evitar isso, proibimos explicitamente o uso das seguintes chaves:
 
 `y`, `Y`, `yes`, `Yes`, `YES`, `n`, `N`, `no`, `No`, `NO`, `true`, `True`, `TRUE`, `false`, `False`, `FALSE`, `on`, `On`, `ON`, `off`, `Off`, `OFF`
 
-The error can be fixed by removing the forbidden keys.
+O erro pode ser corrigido removendo as chaves proibidas.
 
-## Body must contain at least one non-markdown field
+## O texto deve conter pelo menos um campo que não seja markdown
 
-Issue forms must accept user input, which means that at least one of its fields must contain a user input field. A `markdown` element is static text, so a `body` array cannot contain only `markdown` elements.
+Os formulários de problemas devem aceitar a entrada do usuário, o que significa que pelo menos um dos seus campos deve conter um campo de entrada de usuário. Um elemento `markdown` é um texto estático. Portanto, uma matriz do `texto` não pode conter apenas elementos de `markdown`.
 
 ### Exemplo
 
@@ -110,7 +110,7 @@ body:
     value: "Bugs are the worst!"
 ```
 
-The error can be fixed by adding non-markdown elements that accept user input.
+O erro pode ser corrigido adicionando elementos que não são markdown que aceitam a entrada do usuário.
 
 ```yaml
 name: "Bug report"
@@ -123,9 +123,9 @@ body:
     label: "What's wrong?"
 ```
 
-## Body must have unique ids
+## O texto deve ter identificações únicas
 
-If using `id` attributes to distinguish multiple elements, each `id` attribute must be unique.
+Se você estiver usando `atributos de id` para distinguir vários elementos, cada atributo de `id` deverá ser único.
 
 ### Exemplo
 
@@ -142,7 +142,7 @@ body:
     label: Last name
 ```
 
-The error can be fixed by changing the `id` for one of these inputs, so that every `input` field has a unique `id` attribute.
+O erro pode ser corrigido alterando o `id` para uma dessas entradas, para que todo campo `entrada` tenha um atributo `id` único.
 
 ```yaml
 name: "Bug report"
@@ -157,9 +157,9 @@ body:
     label: Last name
 ```
 
-## Body must have unique labels
+## O texto deve ter etiquetas únicas
 
-When there are multiple `body` elements that accept user input, the `label` attribute for each user input field must be unique.
+Quando há vários elementos do `texto` que aceitam entrada do usuário, o atributo `etiqueta` para cada campo de entrada do usuário deve ser único.
 
 ### Exemplo
 
@@ -174,7 +174,7 @@ body:
     label: Name
 ```
 
-The error can be fixed by changing the `label` attribute for one of the input fields to ensure that each `label` is unique.
+O erro pode ser corrigido alterando o atributo `rótulo` para um dos campos de entrada para garantir que cada `etiqueta` seja única.
 
 ```yaml
 name: "Bug report"
@@ -187,7 +187,7 @@ body:
     label: Operating System
 ```
 
-Input fields can also be differentiated by their `id` attribute. If duplicate `label` attributes are required, you can supply at least one `id` to differentiate two elements with identical labels.
+Os campos de entrada também podem ser diferenciados pelo seu atributo `id`. Se forem necessários atributos de `etiquetas` duplicadas, você poderá fornecer pelo menos um `id` para diferenciar dois elementos com etiquetas idênticas.
 
 ```yaml
 name: "Bug report"
@@ -202,7 +202,7 @@ body:
     label: Name
 ```
 
-`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
+Os atributos de `id` não estão visíveis no texto do problema. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
 
 
 ## Labels are too similar
@@ -297,7 +297,7 @@ body:
     - label: Name
 ```
 
-`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
+Os atributos de `id` não estão visíveis no texto do problema. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
 
 ## Body[i]: required key type is missing
 
@@ -418,9 +418,9 @@ The error can be fixed by supplying a string value for `label`. If you want to u
     label: Environment Details
 ```
 
-Empty strings, or strings consisting of only whitespaces, are not permissible when an attribute expects a string. For example, `""` or `"     "` are not allowed.
+As strings vazias ou strings que consistem em apenas espaços em branco não são permitidas quando um atributo espera uma string. Por exemplo, `""` ou `" "` não são permitidos.
 
-If the attribute is required, the value must be a non-empty string. If the field is not required, you should delete the key-value pair.
+Se o atributo é obrigatório, o valor deverá ser uma string não vazia. Se o campo não for obrigatório, você deverá excluir o par chave-valor.
 
 ```yaml
 body:
@@ -429,9 +429,9 @@ body:
     label: "Name"
 ```
 
-## Body[i]: `id` can only contain numbers, letters, -, _
+## Body[i]: `id` pode apenas conter números, letras, -, _
 
-`id` attributes can only contain alphanumeric characters, `-`, and `_`. Your template may include non-permitted characters, such as whitespace, in an `id`.
+Atributos de `id` podem conter apenas caracteres alfanuméricos, `-`, e `_`. Seu modelo pode incluir caracteres não permitidos, como espaços em branco, em um `id`.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
@@ -446,7 +446,7 @@ body:
     label: First name
 ```
 
-The error can be fixed by ensuring that whitespaces and other non-permitted characters are removed from `id` values.
+O erro pode ser corrigido garantindo que os espaços em branco e outros caracteres não permitidos sejam removidos de valores da `id`.
 
 ```yaml
 name: "Bug report"
@@ -457,9 +457,9 @@ body:
     label: First name
 ```
 
-## Body[i]: `x` is not a permitted key
+## Body[i]: `x` não é uma chave permitida
 
-An unexpected key, `x`, was provided at the same indentation level as `type` and `attributes`.
+Uma chave inesperada, `x`, foi fornecida no mesmo nível de indentação que `tipo` e `atributos`.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
@@ -473,7 +473,7 @@ body:
     value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
 ```
 
-The error can be fixed by removing extra keys and only using `type`, `attributes`, and `id`.
+O erro pode ser corrigido removendo chaves extras e usando apenas `tipo`, `atributos` e `id`.
 
 ```yaml
 body:
@@ -482,9 +482,9 @@ body:
     value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
 ```
 
-## Body[i]: `label` contains forbidden word
+## Body[i]: `label` contém a palavra proibida
 
-To minimize the risk of private information and credentials being posted publicly in GitHub Issues, some words commonly used by attackers are not permitted in the `label` of input or textarea elements.
+Para minimizar o risco de informações e credenciais privadas serem publicadas nos problemas do GitHub, algumas palavras comumente usadas por invasores não são permitidas na `etiqueta` de entrada ou elementos de texto.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
@@ -500,7 +500,7 @@ body:
     label: Password
 ```
 
-The error can be fixed by removing terms like "password" from any `label` fields.
+O erro pode ser corrigido removendo termos como "senha" de qualquer campo da `etiqueta`.
 
 ```yaml
 body:
@@ -512,9 +512,9 @@ body:
     label: Username
 ```
 
-## Body[i]: `x` is not a permitted attribute
+## Body[i]: `x` não é um atributo permitido
 
-An invalid key has been supplied in an `attributes` block.
+Uma chave inválida foi fornecida em um bloco de `atributos`.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
@@ -525,10 +525,10 @@ body:
 - type: markdown
   attributes:
     x: "a random key!"
-    value: "Thanks for taking the time to fill out this bug!"
+    valor: "Obrigado por reservar um tempo tempo para preencher esse erro!"
 ```
 
-The error can be fixed by removing extra keys and only using permitted attributes.
+O erro pode ser corrigido removendo chaves extras e usando apenas os atributos permitidos.
 
 ```yaml
 body:
@@ -537,9 +537,9 @@ body:
     value: "Thanks for taking the time to fill out this bug!"
 ```
 
-## Body[i]: `options` must be unique
+## Body[i]: `opções ` devem ser únicas
 
-For checkboxes and dropdown input types, the choices defined in the `options` array must be unique.
+Para caixas de seleção e tipos de entrada de menu suspenso, as escolhas definidas na matriz `opções` devem ser únicas.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
@@ -556,7 +556,7 @@ body:
       - pie
 ```
 
-The error can be fixed by ensuring that no duplicate choices exist in the `options` array.
+O erro pode ser corrigido garantindo que não existam opções duplicadas na matriz de `opções`.
 
 ```
 body:
@@ -568,9 +568,9 @@ body:
       - pie
 ```
 
-## Body[i]: `options` must not include the reserved word, none
+## Body[i]: `options` não deve incluir a palavra reservada, nenhum
 
-"None" is a reserved word in an `options` set because it is used to indicate non-choice when a `dropdown` is not required.
+"Nenhum" é uma palavra reservada em um conjunto de `opções` porque é usado para indicar a não escolha quando não um `dropdown` não é necessário.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
@@ -589,7 +589,7 @@ body:
     required: true
 ```
 
-The error can be fixed by removing "None" as an option. If you want a contributor to be able to indicate that they like none of those types of pies, you can additionally remove the `required` validation.
+O erro pode ser corrigido removendo "Nenhum" como opção. Se você deseja que um contribuidor possa indicar que ele não gosta de nenhum desses tipos de tortas, você pode também remover a validação `necessária`.
 
 ```
 body:
@@ -601,11 +601,11 @@ body:
       - Chicken & Leek
 ```
 
-In this example, "None" will be auto-populated as a selectable option.
+Neste exemplo, "Nenhum" será preenchido automaticamente como uma opção selecionável.
 
-## Body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes
+## Body[i]: `options` não deve incluir booleanos. Por favor, coloque os valores como "sim" e "verdadeiro" entre aspas
 
-There are a number of English words that become processed into Boolean values by the YAML parser unless they are wrapped in quotes. For dropdown `options`, all items must be strings rather than Booleans.
+Há uma série de palavras em inglês processadas em valores booleanos pelo analisador do YAML, a menos que sejam entre aspas. Para as `opções` do menu suspenso, todos os itens devem ser strings ao invés de booleanos.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index 8c73064975..b942f72cf4 100644
--- a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -293,10 +293,10 @@ O parâmetro `redirect_uri` é opcional. Se ignorado, o GitHub redirecionará os
 
 O parâmetro opcional `redirect_uri` também pode ser usado para URLs do localhhost. Se o aplicativo especificar uma URL do localhost e uma porta, após a autorização, os usuários do aplicativo serão redirecionados para a URL e porta fornecidas. O `redirect_uri` não precisa corresponder à porta especificada na URL de retorno de chamada do aplicativo.
 
-Para a URL de retorno de chamada `http://localhost/path`, você poderá usar este `redirect_uri`:
+For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`:
 
 ```
-http://localhost:1234/path
+http://127.0.0.1:1234/path
 ```
 
 ## Criar vários tokens para aplicativos OAuth
diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
index 941cd8fcdf..9caaa92bb5 100644
--- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
+++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -60,4 +60,4 @@ Para obter um exemplo de um fluxo de trabalho de resposta de incidente, consulte
 
 Você deveria realizar varreduras regulares de vulnerabilidades de infraestrutura de produção. Você deve classificar os resultados de verificações de vulnerabilidades e definir um período de tempo no qual você concorda em remediar a vulnerabilidade.
 
-Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)".
+Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)".
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index 086fc51c68..e477a3f6a3 100644
--- a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -45,10 +45,10 @@ You can integrate your personal or organization account on {% data variables.pro
 
 ### Slack and {% data variables.product.product_name %} integration
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. 
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. 
 
 The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace.
 
 ### Microsoft Teams and {% data variables.product.product_name %} integration
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 23d5fdc08f..6c86f05757 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -195,6 +195,8 @@ Use o comando `git remote rm` para remover uma URL remota do seu repositório.
 O comando `git remote rm` tem um argumento:
 * O nome de um remote, como `destination`
 
+Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.
+
 ## Exemplo
 
 Estes exemplos supõem que você está [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), que é o método recomendado.
@@ -217,7 +219,7 @@ $ git remote -v
 
 {% warning %}
 
-**Observação**: o comando `git remote rm` não exclui o repositório do remote no servidor.  Ele simplesmente remove o remote e suas referências do repositório local.
+**Note**: `git remote rm` does not delete the remote repository from the server.  Ele simplesmente remove o remote e suas referências do repositório local.
 
 {% endwarning %}
 
diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md
index 9fea8d3212..0333d708ca 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -37,10 +37,29 @@ Uma licença de {% data variables.product.prodname_GH_advanced_security %} forne
 - **Visão geral de segurança** - Revise a configuração de segurança e os alertas para uma organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".
 {% endif %}
 
+{% ifversion fpt or ghec %}
+The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. |{% ifversion fpt %}
+|                        |          Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %}
+|:----------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:|
+|  Varredura de código   |                 Sim                  |                                         Não                                          |                                        Sim                                        |
+|   Varredura secreta    | Yes **(limited functionality only)** |                                         Não                                          |                                        Sim                                        |
+| Revisão de dependência |                 Sim                  |                                         Não                                          |                                        Sim                                        |{% endif %}
+|
+{% ifversion ghec %}
+|                          |          Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %}
+|:------------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:|
+|   Varredura de código    |                 Sim                  |                                         Não                                          |                                        Sim                                        |
+|    Varredura secreta     | Yes **(limited functionality only)** |                                         Não                                          |                                        Sim                                        |
+|  Revisão de dependência  |                 Sim                  |                                         Não                                          |                                        Sim                                        |
+| Visão geral da segurança |                 Não                  |                                         Não                                          |                                        Sim                                        |
+{% endif %}
+
+{% endif %}
+
 Para obter informações sobre funcionalidades de {% data variables.product.prodname_advanced_security %} em desenvolvimento, consulte "[Plano de trabalho de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para uma visão geral de todas as funcionalidades de segurança, consulte "[ funcionalidades de segurança de{% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
 {% ifversion fpt or ghec %}
-As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão habilitadas para todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. Eles também têm acesso a uma visão geral de segurança a nível da organização. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. They also have access to an organization-level security overview. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
 {% endif %}
 
 {% ifversion ghes or ghec %}
diff --git a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 1903c16a44..cf1ce86ba2 100644
--- a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -25,6 +25,11 @@ Para criar um título, adicione de um a seis símbolos <kbd>#</kbd> antes do tex
 
 ![Títulos H1, H2 e H6 renderizados](/assets/images/help/writing/headings-rendered.png)
 
+When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section.
+
+![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png)
+
+
 ## Estilizar texto
 
 Você pode indicar ênfase com texto em negrito, itálico ou riscado em campos de comentários e arquivos de `.md`.
diff --git a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md
index 37bb94b91a..16621eb4c5 100644
--- a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md
+++ b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md
@@ -22,7 +22,7 @@ A finalidade principal da comunidade do GitHub é colaborar em projetos de softw
 
 * **Seja bem-vindo e venha com a mente aberta!** - Outros colaboradores podem não ter o mesmo nível de experiência ou o mesmo histórico que você, mas isso não significa que eles não tenham boas ideias para contribuir. Nós o encorajamos a receber com boas-vindas os novos colaboradores e aqueles que acabaram de chegar.
 
-* **Respeitem-se.**  Nada sabota tanto as conversas saudáveis quanto a grosseria. Seja cordial e profissional, e não publique nada que uma pessoa de bom senso considere como discurso ofensivo, abusivo ou de ódio. Não assedie ou constranja ninguém. Trate uns aos outros com dignidade e consideração em todas as interações.
+* **Respect each other** - Nothing sabotages healthy conversation like rudeness. Seja cordial e profissional, e não publique nada que uma pessoa de bom senso considere como discurso ofensivo, abusivo ou de ódio. Não assedie ou constranja ninguém. Trate uns aos outros com dignidade e consideração em todas as interações.
 
   Você pode querer responder a algo discordando sobre o assunto. Tudo bem. Mas lembre-se de criticar ideias, não pessoas. Evite xingamentos, ataques diretos ad hominem, respondendo ao tom de um post em vez de seu conteúdo real, e reações impulsivas. Em vez disso, forneça contra-argumentos fundamentados que melhorem a conversa.
 
diff --git a/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md b/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md
index 57477530ca..ee59c92225 100644
--- a/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md
+++ b/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md
@@ -23,3 +23,5 @@ A Política de Marca Registrada do GitHub pode ser utilizada para denunciar cont
 
 ## [Política de Remoção de Informações Privadas do GitHub](/github/site-policy/github-private-information-removal-policy)
 A Política de Remoção de Informações Privadas do GitHub pode ser usada para relatar dados privados (confidenciais e apresenta um risco de segurança), mas isso não é necessariamente protegido por direitos de autor ou por marcas registradas.
+
+Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer).
diff --git a/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md b/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md
index d82f9de964..9456cad5a4 100644
--- a/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md
+++ b/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md
@@ -12,7 +12,7 @@ topics:
 
 ## Visão Geral
 
-Aqui estão alguns links rápidos para ajudá-lo colocar em funcionamento a API v4 do GraphQL:
+Here are some quick links to get you up and running with the GraphQL API:
 
 * [Autenticação](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)
 * [Ponto de extremidade raiz](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint)
@@ -36,9 +36,9 @@ A linguagem de consulta de dados do [GraphQL](https://graphql.github.io/) é:
 
 ## Por que o GitHub está usando GraphQL
 
-O GitHub escolheu o GraphQL para a nossa API v4 porque ele oferece muito mais flexibilidade para os nossos integradores. A capacidade de definir precisamente os dados que você deseja&mdash;e _apenas_ os dados que você quer&mdash;é uma vantagem poderosa dos pontos de extremidades da API REST v3. O GraphQL permite que você substitua várias solicitações de REST por _uma única chamada_ para buscar os dados que você especificar.
+GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want&mdash;and _only_ the data you want&mdash;is a powerful advantage over traditional REST API endpoints. O GraphQL permite que você substitua várias solicitações de REST por _uma única chamada_ para buscar os dados que você especificar.
 
-Para obter mais informações sobre por que o GitHub fez a migração para o GraphQL, consulte o [post de anúncio do blogue](https://githubengineering.com/the-github-graphql-api/) original.
+For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/).
 
 ## Sobre a referência do esquema do GraphQL
 
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
index 6196197d3e..d668ef21f4 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -8,10 +8,10 @@ topics:
   - Organizations
   - Teams
 permissions: Organization owners can access compliance reports for the organization.
-shortTitle: Access compliance reports
+shortTitle: Acessar relatórios de conformidade
 ---
 
-## About {% data variables.product.company_short %}'s compliance reports
+## Sobre os relatórios de conformidade de {% data variables.product.company_short %}
 
 You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
 
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
index 96869d9fe2..808ca34918 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -19,9 +19,9 @@ shortTitle: Revisar integrações instaladas
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
-{% elsif ghae or ghes < 3.4 %}
+{% else %}
 1. Na barra lateral esquerda, clique em **{% data variables.product.prodname_github_apps %} instalado**. ![Aba de {% data variables.product.prodname_github_apps %} instalada na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 {% endif %}
 2. Próximo do {% data variables.product.prodname_github_app %} que deseja revisar, clique em **Configure** (Configurar). ![Botão Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png)
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index 6c93e16be0..5747fb67d6 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -40,7 +40,7 @@ Para apoiar ainda mais as habilidades de colaboração da sua equipe, você pode
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field.png)
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 10bfe07afc..5c530ecbb0 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -28,9 +28,9 @@ Ao remover um colaborador de um repositório de sua organização, o colaborador
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
 {% data reusables.organizations.invite-teams-or-people %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index 08391639b1..7f6f020979 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -24,7 +24,7 @@ Quando você desabilita quadros de projeto, deixa de ver informações relaciona
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
 {% endif %}
 1. Decida se deseja desabilitar quadros de projeto em toda a organização, desabilitar quadros de projeto de repositório na organização ou ambos. Em seguida, em "Projects" (Projetos):
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
index 0020d467c3..84ff510c04 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -10,12 +10,12 @@ versions:
 shortTitle: Integrate Jira
 ---
 
-{% ifversion ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. ![Aba OAuth applications (aplicativos OAuth) na barra lateral esquerda](/assets/images/help/organizations/org-oauth-applications-ghe.png)
 1. Clique em **Novo aplicativo OAuth**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 {% data reusables.user_settings.access_settings %}
 1. Na barra lateral esquerda, em **Organization settings** (Configurações da organização) clique no nome de sua organização. ![Barra lateral organization name (nome da organização)](/assets/images/help/settings/organization-settings-from-sidebar.png)
 1. Na barra lateral esquerda, em **Developer settings** (Configurações do desenvolvedor), clique em **OAuth applications** (Aplicativos OAuth) ![Aba OAuth applications (aplicativos OAuth) na barra lateral esquerda](/assets/images/help/organizations/org-oauth-applications-ghe.png)
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index 49256606f0..8627a8be51 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -15,11 +15,15 @@ topics:
 shortTitle: Restringir criação de repositório
 ---
 
-Você pode escolher se os integrantes podem criar repositórios na sua organização. Se você permitir que os integrantes criem repositórios, você poderá escolher quais tipos de repositórios os integrantes poderão criar.{% ifversion fpt or ghec %} Para permitir que os integrantes criem apenas repositórios privados, a sua organização deve usar {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} Para obter mais informações, consulte "[Sobre repositórios](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" na documentação de {% data variables.product.prodname_ghe_cloud %}{% endif %}.
+Você pode escolher se os integrantes podem criar repositórios na sua organização. {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository.
+
+{% ifversion fpt %}
+Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization).
+{% endif %}
 
-Os proprietários da organização sempre podem criar qualquer tipo de repositório.
 {% ifversion ghec or ghae or ghes %}
-{% ifversion ghec or ghae %}Proprietários corporativos{% elsif ghes %}administradores do site{% endif %} podem restringir as opções que você tem disponíveis para a política de criação de repositório da sua organização.{% ifversion ghec or ghes or ghae %} Para obter mais informações, consulte "[Restringindo a criação de repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
+Enterprise owners can restrict the options you have available for your organization's repository creation policy. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)".
+{% endif %}
 
 {% warning %}
 
@@ -36,5 +40,12 @@ Os proprietários da organização sempre podem criar qualquer tipo de repositó
    ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
    ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+
+   {% note %}
+
+   **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.
+
+   {% endnote %}
    {%- endif %}
+
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 140910d545..f823d2feba 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -57,7 +57,7 @@ Todos os integrantes da equipe que definiram seu status como "Ocupado" não ser
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Revisão de Código** ![Botão revisar código](/assets/images/help/teams/review-button.png)
@@ -71,7 +71,7 @@ Todos os integrantes da equipe que definiram seu status como "Ocupado" não ser
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Revisão de Código** ![Botão revisar código](/assets/images/help/teams/review-button.png)
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index b205d0b9da..bb1babbfdb 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -22,7 +22,7 @@ topics:
 
 **Observação:** ao trabalhar com pull requests, lembre-se do seguinte:
 * Se estiver trabalhando no [modo de repositório compartilhado](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), é recomendável usar um branch de tópico para sua pull request. Embora você possa enviar pull requests de qualquer branch ou commit, com um branch de tópico, é possível fazer push de commits de acompanhamento caso seja preciso atualizar as alterações propostas.
-* Ao fazer push de commits para uma pull request, não force o push. Faz push forçado das alterações no histórico do repositório e pode corromper o seu pull request. Se outros colaboradores fizerem o branch do projeto antes de um push forçado, este poderá substituir os commits nos quais os colaboradores basearam o seu trabalho.
+* Be very careful when force pushing commits to a pull request. Faz push forçado das alterações no histórico do repositório e pode corromper o seu pull request. Se outros colaboradores fizerem o branch do projeto antes de um push forçado, este poderá substituir os commits nos quais os colaboradores basearam o seu trabalho.
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index 98c84b7427..97e3527e29 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -17,7 +17,7 @@ topics:
 
 Bifurcar um repositório é semelhante a copiar um repositório, com duas grandes diferenças:
 
-* Você pode usar uma pull request para sugerir alterações da sua bifurcação user-owned para o repositório original, também conhecido como o repositório *upstream*.
+* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository.
 * Você pode transmitir alterações do repositório upstream para a sua bifurcação local sincronizando a bifurcação com o repositório upstream.
 
 {% data reusables.repositories.you-can-fork %}
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index b00a22be19..be5773f6bc 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -18,7 +18,7 @@ topics:
 
 As pessoas com permissões de administrador ou proprietário podem configurar um arquivo CODEOWNERS em um repositório.
 
-As pessoas que você escolhe como proprietários do código devem ter permissões de gravação para o repositório. Quando o proprietário do código é uma equipe, essa equipe deverá ser visível e ter permissões de gravação, ainda que todos os membros individuais da equipe já tenham permissões de gravação diretamente, por meio da associação da organização ou por meio de outra associação à equipe.
+The people you choose as code owners must have read permissions for the repository. Quando o proprietário do código é uma equipe, essa equipe deverá ser visível e ter permissões de gravação, ainda que todos os membros individuais da equipe já tenham permissões de gravação diretamente, por meio da associação da organização ou por meio de outra associação à equipe.
 
 ## Sobre proprietários do código
 
@@ -104,11 +104,11 @@ apps/ @octocat
 # will require approval from @doctocat or @octocat.
 /scripts/ @doctocat @octocat
 
-# In this example, @octocat owns any file in the `/apps` 
-# directory in the root of your repository except for the `/apps/github` 
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
 # subdirectory, as its owners are left empty.
 /apps/ @octocat
-/apps/github 
+/apps/github
 ```
 ### Exceções de sintaxe
 Existem algumas regras de sintaxe para arquivos gitignore que não funcionam em arquivos CODEOWNERS:
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
index 38d656eeba..ef402a1785 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -22,7 +22,7 @@ Se você usa o Zendesk para acompanhar tíquetes relatados pelo usuário, por ex
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Autolink references** (Referências de link automático). ![Guia Autolink references (Referências de link automático) na barra lateral esquerda](/assets/images/help/repository/autolink-references-tab.png)
diff --git a/translations/pt-BR/content/rest/reference/billing.md b/translations/pt-BR/content/rest/reference/billing.md
index ed6cb4eda8..5cd7d7d8d5 100644
--- a/translations/pt-BR/content/rest/reference/billing.md
+++ b/translations/pt-BR/content/rest/reference/billing.md
@@ -4,6 +4,7 @@ intro: 'Com a API de cobrança você pode monitorar as cobranças e uso {% data
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '>=3.4'
 topics:
   - API
 miniTocMaxHeadingLevel: 3
diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md
index 006d78ee79..230e3f76b5 100644
--- a/translations/pt-BR/content/rest/reference/enterprise-admin.md
+++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md
@@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer
 
 {% endif %}
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 %}
 ## Billing
 
 {% for operation in currentRestOperations %}
diff --git a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
index 03a6f893eb..5c4de1fea8 100644
--- a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
+++ b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
@@ -2,6 +2,8 @@
    1. Você deve fornecer, pelo menos, o nome para o seu padrão e uma expressão regular para o formato do seu padrão de segredo.
    1. Você pode clicar em **Mais opções {% octicon "chevron-down" aria-label="down" %}** para fornecer outros conteúdos adjacentes ou requisitos adicionais de correspondência para o formato do segredo.
    1. Provide a sample test string to make sure your configuration is matching the patterns you expect.
-
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}
    ![Crie um formulário de padrão personalizado de {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/secret-scanning-create-custom-pattern.png)
-1. When you are satisfied with your new custom pattern, click {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}.
+   {% else %}
+   ![Crie um formulário de padrão personalizado de {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png)
+   {% endif %}
diff --git a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
new file mode 100644
index 0000000000..8f4453f9fc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
@@ -0,0 +1 @@
+1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern**{% elsif  ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}.
diff --git a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index c245d3ddbe..a763a75baf 100644
--- a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else  %}
 1. Na barra lateral Settings, clique em **Audit log**. ![Configurações de log de auditoria para organizações na barra lateral](/assets/images/help/organizations/org-settings-audit-log.png)
diff --git a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index b410a8053c..0f6217e1da 100644
--- a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 3. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else  %}
 3. Na barra lateral esquerda, clique em **Audit log**. ![Aba Log de auditoria](/assets/images/enterprise/site-admin-settings/audit-log-tab.png)
diff --git a/translations/pt-BR/data/reusables/billing/email-notifications.md b/translations/pt-BR/data/reusables/billing/email-notifications.md
index e6dfecd285..4b134cf465 100644
--- a/translations/pt-BR/data/reusables/billing/email-notifications.md
+++ b/translations/pt-BR/data/reusables/billing/email-notifications.md
@@ -1,3 +1,5 @@
-As notificações de e-mail são enviadas para os proprietários de contas e gerentes de cobrança quando os gastos chegam a 50%, 75%, e 90% do uso incluído na sua conta e quando os gastos chegam a 50%, 75%, e 90% do limite de gastos da sua conta.
+Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
 
 Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**.
+
+![Screenshot of the billing email notification settings](/assets/images/help/billing/actions-packages-spending-limit-notifications.png)
diff --git a/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md b/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md
index ec922b1ac5..c97cd90ae3 100644
--- a/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md
+++ b/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
-{% elsif ghes > 3.2%}
+{% else %}
 1. Na barra lateral, clique em **{% data variables.product.prodname_dependabot %}**. ![Opção da barra lateral de segredos de {% data variables.product.prodname_dependabot %}](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md b/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md
index 6a6e7a60ed..81a27e5660 100644
--- a/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md
+++ b/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md
@@ -1,6 +1,6 @@
 {% note %}
 
-**Nota:** se seus fluxos de trabalho usam ações do contêiner Docker ou recipientes de serviço, você deve usar um executor Linux:
+**Note:** If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runner:
 
 * Se você estiver usando executores hospedados em {% data variables.product.prodname_dotcom %}, você deverá usar um executor do Ubuntu.
 * Se você estiver usando executores auto-hospedados, você deve usar uma máquina Linux, pois seu executor e o Docker precisam ser instalados.
diff --git a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
index 0a29042def..da96012798 100644
--- a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
@@ -5,8 +5,8 @@ permissions:
   actions: read|write|none
   checks: read|write|none
   contents: read|write|none
-  deployments: read|write|none
-  id-token: read|write|none
+  deployments: read|write|none{% ifversion fpt or ghec %}
+  id-token: read|write|none{% endif %}
   issues: read|write|none
   discussions: read|write|none
   packages: read|write|none
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
index 1c973c16c3..d25129f56e 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
+++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
@@ -12,6 +12,6 @@
      2. Na barra lateral esquerda, clique em **Visão geral da empresa**.
      3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
 2. Navigate to the "Runner groups" settings:
-   * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %}
-   * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghec %}, then click the **Runners groups** tab{% endif %}.{% endif %}
+   * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %}
+   * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %}
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md b/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md
index 4adf6c9661..e23fedb78a 100644
--- a/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md
+++ b/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral esquerda, clique em **Secrets** (Segredos).
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/billing_plans.md b/translations/pt-BR/data/reusables/organizations/billing_plans.md
index 2ea9a5cf17..6036159319 100644
--- a/translations/pt-BR/data/reusables/organizations/billing_plans.md
+++ b/translations/pt-BR/data/reusables/organizations/billing_plans.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral das configurações da sua organização, clique em **Planos de & cobrança**. ![Configurações de faturamento](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md
index ed09054fd9..2e8823aed8 100644
--- a/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md
+++ b/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral esquerda, clique em **{% data variables.product.prodname_github_apps %}**. ![{% data variables.product.prodname_github_apps %} settings](/assets/images/help/organizations/github-apps-settings-sidebar.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/member-privileges.md b/translations/pt-BR/data/reusables/organizations/member-privileges.md
index fdd8fe2a7a..c791a7b7ab 100644
--- a/translations/pt-BR/data/reusables/organizations/member-privileges.md
+++ b/translations/pt-BR/data/reusables/organizations/member-privileges.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
-{% elsif ghae or ghes < 3.4 %}
+{% else %}
 4. Na barra lateral esquerda, clique em **Member privileges** (Privilégios de membro). ![Opção de privilégios de membro nas configurações do org](/assets/images/help/organizations/org-settings-member-privileges.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/repository-defaults.md b/translations/pt-BR/data/reusables/organizations/repository-defaults.md
index 6d44f46f55..391a6a4ad0 100644
--- a/translations/pt-BR/data/reusables/organizations/repository-defaults.md
+++ b/translations/pt-BR/data/reusables/organizations/repository-defaults.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral esquerda, clique em **Padrões do repositório**. ![Aba Padrão do repositório](/assets/images/help/organizations/repo-defaults-tab.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/security-and-analysis.md b/translations/pt-BR/data/reusables/organizations/security-and-analysis.md
index d0199f4410..77a2d097d4 100644
--- a/translations/pt-BR/data/reusables/organizations/security-and-analysis.md
+++ b/translations/pt-BR/data/reusables/organizations/security-and-analysis.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral esquerda, clique em **Security & analysis** (Segurança e análise). !["Security & analysis" (Segurança e análise) aba nas configurações da organização](/assets/images/help/organizations/org-settings-security-and-analysis.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/security.md b/translations/pt-BR/data/reusables/organizations/security.md
index 2d0a9d68f6..209240ce4f 100644
--- a/translations/pt-BR/data/reusables/organizations/security.md
+++ b/translations/pt-BR/data/reusables/organizations/security.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
 {% else  %}
 1. Na barra lateral esquerda, clique em **Organization security** (Segurança da organização).
diff --git a/translations/pt-BR/data/reusables/organizations/teams_sidebar.md b/translations/pt-BR/data/reusables/organizations/teams_sidebar.md
index 31946ac488..a5a4901c03 100644
--- a/translations/pt-BR/data/reusables/organizations/teams_sidebar.md
+++ b/translations/pt-BR/data/reusables/organizations/teams_sidebar.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
 {% else %}
 1. Na barra lateral de configurações, clique em **Teams** (Equipes). ![Aba de equipes na barra lateral de configurações da organização](/assets/images/help/settings/settings-sidebar-team-settings.png)
diff --git a/translations/pt-BR/data/reusables/organizations/verified-domains.md b/translations/pt-BR/data/reusables/organizations/verified-domains.md
index a10c7d9319..c79c87de48 100644
--- a/translations/pt-BR/data/reusables/organizations/verified-domains.md
+++ b/translations/pt-BR/data/reusables/organizations/verified-domains.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral esquerda, clique em **Domínios & verificados e aprovados**. ![Aba "& domínios aprovados" verificados](/assets/images/help/organizations/verified-domains-button.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/pages/sidebar-pages.md b/translations/pt-BR/data/reusables/pages/sidebar-pages.md
index ec65e49f5d..0238f6860b 100644
--- a/translations/pt-BR/data/reusables/pages/sidebar-pages.md
+++ b/translations/pt-BR/data/reusables/pages/sidebar-pages.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %}
+{% ifversion fpt or ghes > 3.4 or ghec or ghae-issue-5658 %}
 1. In the "Code & operations" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Aba de páginas na barra lateral esquerda](/assets/images/help/pages/pages-tab.png)
diff --git a/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md
index 5eaf9fe7ed..aa2db8b271 100644
--- a/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md
+++ b/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. Na barra lateral esquerda, clique em **Security & analysis** (Segurança e análise). ![aba de "Segurança & análise" nas configurações do repositório](/assets/images/help/repository/security-and-analysis-tab.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/repositories/repository-branches.md b/translations/pt-BR/data/reusables/repositories/repository-branches.md
index a93e602225..2922f65439 100644
--- a/translations/pt-BR/data/reusables/repositories/repository-branches.md
+++ b/translations/pt-BR/data/reusables/repositories/repository-branches.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. No menu à esquerda, clique em **Branches**. ![Submenu de opções do repositório](/assets/images/help/repository/repository-options-branch.png)
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md b/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md
index 2e387d66c7..2b9aee5409 100644
--- a/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
 {% else %}
 1. Clique em **Notificações**. ![Botão de notificações na barra lateral](/assets/images/help/settings/notifications_menu.png)
diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta-dry-runs.md b/translations/pt-BR/data/reusables/secret-scanning/beta-dry-runs.md
new file mode 100644
index 0000000000..2d3121b0cd
--- /dev/null
+++ b/translations/pt-BR/data/reusables/secret-scanning/beta-dry-runs.md
@@ -0,0 +1,6 @@
+
+{% note %}
+
+**Note:** The dry run feature is currently in beta and subject to change.
+
+{% endnote %}
diff --git a/translations/pt-BR/data/reusables/user_settings/access_applications.md b/translations/pt-BR/data/reusables/user_settings/access_applications.md
index 7db741ea14..88ce4b3829 100644
--- a/translations/pt-BR/data/reusables/user_settings/access_applications.md
+++ b/translations/pt-BR/data/reusables/user_settings/access_applications.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Applications** (Aplicativos). ![Aba aplicativos](/assets/images/help/settings/settings-applications.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/account_settings.md b/translations/pt-BR/data/reusables/user_settings/account_settings.md
index ced72b8186..5c2f9130ac 100644
--- a/translations/pt-BR/data/reusables/user_settings/account_settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/account_settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-next %}
 1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Conta**. ![Opção do menu configurações da conta](/assets/images/help/settings/settings-sidebar-account-settings.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/appearance-settings.md b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
index 050370bf13..1969c21932 100644
--- a/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
-1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
+1. Na barra lateral esquerda, clique em **Aparência de {% octicon "paintbrush" aria-label="The paintbrush icon" %}**.
 {% else %}
 1. Na barra lateral de configurações do usuário, clique em **Aparência**.
 
diff --git a/translations/pt-BR/data/reusables/user_settings/developer_settings.md b/translations/pt-BR/data/reusables/user_settings/developer_settings.md
index a7c3a03398..90e3bdeb9c 100644
--- a/translations/pt-BR/data/reusables/user_settings/developer_settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/developer_settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Developer settings** (Configurações do desenvolvedor). ![Configurações do desenvolvedor](/assets/images/help/settings/developer-settings.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/emails.md b/translations/pt-BR/data/reusables/user_settings/emails.md
index ede0a651c5..30276c145e 100644
--- a/translations/pt-BR/data/reusables/user_settings/emails.md
+++ b/translations/pt-BR/data/reusables/user_settings/emails.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
 {% else %}
 1. Na barra lateral esquerda, clique em **E-mails**. ![Aba de e-mails](/assets/images/help/settings/settings-sidebar-emails.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/organizations.md b/translations/pt-BR/data/reusables/user_settings/organizations.md
index 2e922b6ced..56e71f320f 100644
--- a/translations/pt-BR/data/reusables/user_settings/organizations.md
+++ b/translations/pt-BR/data/reusables/user_settings/organizations.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% else %}
 1. Na barra lateral de configurações do usuário, clique em **Organizações**. ![Configurações do usuário para organizações](/assets/images/help/settings/settings-user-orgs.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/repo-tab.md b/translations/pt-BR/data/reusables/user_settings/repo-tab.md
index bba693a256..dfca42af6f 100644
--- a/translations/pt-BR/data/reusables/user_settings/repo-tab.md
+++ b/translations/pt-BR/data/reusables/user_settings/repo-tab.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Repositories** (Repositórios). ![Guia Repositories (Repositórios)](/assets/images/help/settings/repos-tab.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/saved_replies.md b/translations/pt-BR/data/reusables/user_settings/saved_replies.md
index 4518824f63..8c89dbb57f 100644
--- a/translations/pt-BR/data/reusables/user_settings/saved_replies.md
+++ b/translations/pt-BR/data/reusables/user_settings/saved_replies.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Respostas salvas**. ![Aba de respostas salvas](/assets/images/help/settings/saved-replies-tab.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/security-analysis.md b/translations/pt-BR/data/reusables/user_settings/security-analysis.md
index 642735a0f6..aec1ce067f 100644
--- a/translations/pt-BR/data/reusables/user_settings/security-analysis.md
+++ b/translations/pt-BR/data/reusables/user_settings/security-analysis.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
 {% else %}
 1. Na barra lateral esquerda, clique em **Security & analysis** (Segurança e análise). ![Configurações de segurança e análise](/assets/images/help/settings/settings-sidebar-security-analysis.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/security.md b/translations/pt-BR/data/reusables/user_settings/security.md
index 5fd1ae50cd..fdc2ac26ab 100644
--- a/translations/pt-BR/data/reusables/user_settings/security.md
+++ b/translations/pt-BR/data/reusables/user_settings/security.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
 {% else %}
 1. Na barra lateral esquerda, clique em **segurança da conta**. ![Configurações de segurança da conta do usuário](/assets/images/help/settings/settings-sidebar-account-security.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/ssh.md b/translations/pt-BR/data/reusables/user_settings/ssh.md
index 2ba12f8b8c..5122dd314e 100644
--- a/translations/pt-BR/data/reusables/user_settings/ssh.md
+++ b/translations/pt-BR/data/reusables/user_settings/ssh.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
 {% else %}
 1. Na barra lateral de configurações do usuário, clique em **chaves SSH e GPG**. ![Chaves de autenticação](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index c9f2898800..c8a8983573 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -38,7 +38,7 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
 1. 您邀请成为协作者的人员需提供用户名。{% ifversion fpt or ghec %} 如果他们还没有用户名，他们可以注册 {% data variables.product.prodname_dotcom %} 更多信息请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”。{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%}
 {% data reusables.repositories.click-collaborators-teams %}
 1. 单击 **Invite a collaborator（邀请协作者）**。 !["邀请协作者" 按钮](/assets/images/help/repository/invite-a-collaborator-button.png)
 2. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 ![搜索字段以键入要邀请加入仓库的人员姓名](/assets/images/help/repository/manage-access-invite-search-field-user.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 3bd5abf224..7587fc0c4d 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -30,7 +30,7 @@ shortTitle: 删除协作者
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
 4. 在要要删除的协作者的右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 ![用于删除协作者的按钮](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 564c5f2715..30a8d93923 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -21,7 +21,7 @@ shortTitle: 删除自己
 ---
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
 {% else %}
 2. 在左侧边栏中，单击 **Repositories（仓库）**。 ![仓库选项卡](/assets/images/help/settings/settings-sidebar-repositories.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index 5ed66d24b6..586f705ff5 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -22,7 +22,7 @@ shortTitle: 管理主题设置
 
 {% note %}
 
-**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
+**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index ca3c04e8dc..15b7173f8f 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -69,7 +69,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Build with Gradle
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: build
 ```
@@ -106,7 +106,7 @@ steps:
   - name: Validate Gradle wrapper
     uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
   - name: Run the Gradle package task
-    uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+    uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
     with:
       arguments: -b ci.gradle package
 ```
@@ -135,7 +135,7 @@ steps:
   - name: Validate Gradle wrapper
     uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
   - name: Build with Gradle
-    uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+    uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
     with:
       arguments: build
   - uses: actions/upload-artifact@v2
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
index 58f6227adc..5fabeae91b 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -56,7 +56,7 @@ shortTitle: Docker 容器操作
 
 ## 创建 Dockerfile
 
-在新的 `hello-world-docker-action` 目录中，创建新的 `Dockerfile` 文件。 Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。
+在新的 `hello-world-docker-action` 目录中，创建新的 `Dockerfile` 文件。 如果您有问题，请确保您的文件名正确大写（使用大写字母 `D` 但不要大写 `f`）。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。
 
 **Dockerfile**
 ```Dockerfile{:copy}
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
index 3952af62a5..e25ab3e0d1 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
@@ -37,7 +37,7 @@ shortTitle: JavaScript 操作
 
 在开始之前，您需要下载 Node.js 并创建公共 {% data variables.product.prodname_dotcom %} 仓库。
 
-1. Download and install Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}, which includes npm.
+1. 下载并安装 Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}，其中包含 npm。
 
   {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
 
diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 6d78d67c1b..2e70f1799d 100644
--- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -47,7 +47,7 @@ Docker 操作必须由默认 Docker 用户 (root) 运行。 不要在 `Dockerfil
 
 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。 有关 _exec_ 和 _shell_ 形式的更多信息，请参阅 Docker 文档中的 [ENTRYPOINT 参考](https://docs.docker.com/engine/reference/builder/#entrypoint)。
 
-You should not use `WORKDIR` to specify your entrypoint in your Dockerfile. Instead, you should use an absolute path. For more information, see [WORKDIR](#workdir).
+您不应使用 `WORKDIR` 在 Dockerfile 中指定入口点。 而应使用绝对路径。 更多信息请参阅 [WORKDIR](#workdir)。
 
 如果您配置容器使用 _exec_ 形式的 `ENTRYPOINT` 指令，在操作元数据文件中配置的 `args` 不会在命令 shell 中运行。 如果操作的 `args` 包含环境变量，不会替换该变量。 例如，使用以下 _exec_ 格式将不会打印存储在 `$GITHUB_SHA` 中的值， 但会打印 `"$GITHUB_SHA"`。
 
diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 24c80f1a28..f018198405 100644
--- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 4
 
 ## 关于 {% data variables.product.prodname_actions %} 的 YAML 语法
 
-All actions require a metadata file. 元数据文件名必须是 `action.yml` 或 `action.yaml`。 The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
+所有操作都需要元数据文件。 元数据文件名必须是 `action.yml` 或 `action.yaml`。 元数据文件中的数据定义操作的输入、输出和运行配置。
 
 操作元数据文件使用 YAML 语法。 如果您是 YAML 的新用户，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。
 
@@ -41,7 +41,7 @@ All actions require a metadata file. 元数据文件名必须是 `action.yml` 
 
 **可选** 输入参数用于指定操作在运行时预期使用的数据。 {% data variables.product.prodname_dotcom %} 将输入参数存储为环境变量。 大写的输入 ID 在运行时转换为小写。 建议使用小写输入 ID。
 
-### Example: Specifying inputs
+### 示例：指定输入
 
 此示例配置两个输入：numOctocats 和 octocatEyeColor。 numOctocats 输入不是必要的，默认值为 '1'。 octocatEyeColor 输入是必要的，没有默认值。 使用此操作的工作流程文件必须使用 `with` 关键词来设置 octocatEyeColor 的输入值。 有关 `with` 语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)”。
 
@@ -84,13 +84,13 @@ inputs:
 
 **可选** 如果使用输入参数，此 `string` 将记录为警告消息。 您可以使用此警告通知用户输入已被弃用，并提及任何其他替代方式。
 
-## `outputs` for Docker container and JavaScript actions
+## 用于 Docker 容器和 JavaScript 操作的 `outputs`
 
 **可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。  例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。
 
 如果不在操作元数据文件中声明输出，您仍然可以设置输出并在工作流程中使用它们。 有关在操作中设置输出的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)”。
 
-### Example: Declaring outputs for Docker container and JavaScript actions
+### 示例：声明 Docker 容器和 JavaScript 操作的输出
 
 ```yaml
 outputs:
@@ -108,11 +108,17 @@ outputs:
 
 ## 用于复合操作的 `outputs`
 
-**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
+**可选** `outputs` 使用与 `outputs.<output_id>` 及 `outputs.<output_id>.description` 相同的参数（请参阅“用于 Docker 容器和 JavaScript 操作的
 
-### Example: Declaring outputs for composite actions
+`outputs`”），但也包括 `value` 令牌。</p> 
+
+
+
+### 示例：声明复合操作的 outputs
 
 {% raw %}
+
+
 ```yaml
 outputs:
   random-number:
@@ -125,23 +131,35 @@ runs:
       run: echo "::set-output name=random-id::$(echo $RANDOM)"
       shell: bash
 ```
+
+
 {% endraw %}
 
+
+
 ### `outputs.<output_id>.value`
 
 **必要** 输出参数将会映射到的值。 您可以使用上下文将此设置为 `string` 或表达式。 例如，您可以使用 `steps` 上下文将输出的 `value` 设置为步骤的输出值。
 
 有关如何使用上下文语法的更多信息，请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
+
+
 ## `runs`
 
-**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed.
+**必要** 指定这是 JavaScript 操作、复合操作还是 Docker 容器操作以及操作的执行方式。
+
+
 
 ## 用于 JavaScript 操作的 `runs`
 
-**Required** Configures the path to the action's code and the runtime used to execute the code.
+**必要** 配置操作代码的路径和用于执行代码的运行时。
+
+
+
+### 示例：使用 Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
+
 
-### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
 ```yaml
 runs:
@@ -149,23 +167,32 @@ runs:
   main: 'main.js'
 ```
 
+
+
+
 ### `runs.using`
 
-**Required** The runtime used to execute the code specified in [`main`](#runsmain).
+**Required** The runtime used to execute the code specified in [`main`](#runsmain).  
 
 - Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 - Use `node16` for Node.js v16.{% endif %}
 
+
+
 ### `runs.main`
 
 **必要** 包含操作代码的文件。 The runtime specified in [`using`](#runsusing) executes this file.
 
+
+
 ### `runs.pre`
 
 **可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
 
 在此示例中，`pre:` 操作运行名为 `setup.js` 的脚本：
 
+
+
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
@@ -174,6 +201,9 @@ runs:
   post: 'cleanup.js'
 ```
 
+
+
+
 ### `runs.pre-if`
 
 **可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
@@ -182,17 +212,24 @@ runs:
 
 在此示例中，`cleanup.js` 仅在基于 Linux 的运行器上运行：
 
+
+
 ```yaml
   pre: 'cleanup.js'
   pre-if: runner.os == 'linux'
 ```
 
+
+
+
 ### `runs.post`
 
 **可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
 在此示例中，`post:` 操作会运行名为 `cleanup.js` 的脚本：
 
+
+
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
@@ -200,44 +237,70 @@ runs:
   post: 'cleanup.js'
 ```
 
+
 `post:` 操作始终默认运行，但您可以使用 `post-if` 覆盖该设置。
 
+
+
 ### `runs.post-if`
 
 **可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 In `post-if`, status check functions evaluate against the job's status, not the action's own status.
 
 例如，此 `cleanup.js` 仅在基于 Linux 的运行器上运行：
 
+
+
 ```yaml
   post: 'cleanup.js'
   post-if: runner.os == 'linux'
 ```
 
+
+
+
 ## 用于复合操作的 `runs`
 
 **Required** Configures the path to the composite action.
 
+
+
 ### `runs.using`
 
 **Required** You must set this value to `'composite'`.
 
+
+
 ### `runs.steps`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。
+
+
+**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。 
+
 {% else %}
-**必要** 您计划在此操作中的步骤。
+
+**必要** 您计划在此操作中的步骤。 
+
 {% endif %}
 
+
+
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
+
+
+**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
+
 {% else %}
-**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
+
+**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
+
 {% endif %}
 
 {% raw %}
+
+
 ```yaml
 runs:
   using: "composite"
@@ -245,10 +308,14 @@ runs:
     - run: ${{ github.action_path }}/test/script.sh
       shell: bash
 ```
+
+
 {% endraw %}
 
 或者，您也可以使用 `$GITHUB_ACTION_PATH`：
 
+
+
 ```yaml
 runs:
   using: "composite"
@@ -257,17 +324,27 @@ runs:
       shell: bash
 ```
 
+
 更多信息请参阅“[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
 
+
+
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
+
+
+**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
+
 {% else %}
-**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
+
+**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
+
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
+
+
 #### `runs.steps[*].if`
 
 **Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 您可以使用任何支持上下文和表达式来创建条件。
@@ -276,7 +353,9 @@ runs:
 
 **示例：使用上下文**
 
- 此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
+此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
+
+
 
  ```yaml
 steps:
@@ -284,10 +363,13 @@ steps:
     if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
 ```
 
+
 **示例：使用状态检查功能**
 
 The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
 
+
+
 ```yaml
 steps:
   - name: My first step
@@ -296,36 +378,51 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
     uses: actions/heroku@1.0.0
 ```
+
+
 {% endif %}
 
+
+
 #### `runs.steps[*].name`
 
 **可选** 复合步骤的名称。
 
+
+
 #### `runs.steps[*].id`
 
 **可选** 步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
+
+
 #### `runs.steps[*].env`
 
 **可选** 设置环境变量的 `map` 仅用于该步骤。 If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
 
+
+
 #### `runs.steps[*].working-directory`
 
 **可选**  指定命令在其中运行的工作目录。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
+
+
 #### `runs.steps[*].uses`
 
 **可选**  选择作为作业步骤一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。
 
 强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。
+
 - 使用已发行操作版本的 SHA 对于稳定性和安全性是最安全的。
 - 使用特定主要操作版本可在保持兼容性的同时接收关键修复和安全补丁。 还可确保您的工作流程继续工作。
 - 使用操作的默认分支可能很方便，但如果有人新发布具有突破性更改的主要版本，您的工作流程可能会中断。
 
 有些操作要求必须通过 [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) 关键词设置输入。 请查阅操作的自述文件，确定所需的输入。
 
+
+
 ```yaml
 runs:
   using: "composite"
@@ -348,10 +445,15 @@ runs:
     - uses: docker://alpine:3.8
 ```
 
+
+
+
 #### `runs.steps[*].with`
 
 **可选** 输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。  输入参数被设置为环境变量。 该变量的前缀为 INPUT_，并转换为大写。
 
+
+
 ```yaml
 runs:
   using: "composite"
@@ -363,32 +465,50 @@ runs:
         middle_name: The
         last_name: Octocat  
 ```
+
+
 {% endif %}
 
+
+
 ## `runs` for Docker container actions
 
 **Required** Configures the image used for the Docker container action.
 
+
+
 ### Example: Using a Dockerfile in your repository
 
+
+
 ```yaml
 runs:
   using: 'docker'
   image: 'Dockerfile'
 ```
 
+
+
+
 ### Example: Using public Docker registry container
 
+
+
 ```yaml
 runs:
   using: 'docker'
   image: 'docker://debian:stretch-slim'
 ```
 
+
+
+
 ### `runs.using`
 
 **必要** 必须将此值设置为 `'docker'`。
 
+
+
 ### `runs.pre-entrypoint`
 
 **可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
@@ -397,6 +517,8 @@ The runtime specified with the [`using`](#runsusing) syntax will execute this fi
 
 在此示例中，`pre-entrypoint:` 操作会运行名为 `setup.sh` 的脚本：
 
+
+
 ```yaml
 runs:
   using: 'docker'
@@ -407,24 +529,35 @@ runs:
   entrypoint: 'main.sh'
 ```
 
+
+
+
 ### `runs.image`
 
 **必要** 要用作容器来运行操作的 Docker 映像。 值可以是 Docker 基本映像名称、仓库中的本地 `Dockerfile`、Docker Hub 中的公共映像或另一个注册表。 要引用仓库本地的 `Dockerfile`，文件必须命名为 `Dockerfile`，并且您必须使用操作元数据文件的相对路径。 `Docker` 应用程序将执行此文件。
 
+
+
 ### `runs.env`
 
 **可选** 指定要在容器环境中设置的环境变量的键/值映射。
 
+
+
 ### `runs.entrypoint`
 
 **可选** 覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 当 `Dockerfile` 未指定 `ENTRYPOINT` 或者您想要覆盖 `ENTRYPOINT` 指令时使用 `entrypoint`。 如果您省略 `entrypoint`，您在 Docker `ENTRYPOINT` 指令中指定的命令将执行。 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。
 
 有关 `entrypoint` 如何执行的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)”。
 
+
+
 ### `post-entrypoint`
 
 **可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为  {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
 
+
+
 ```yaml
 runs:
   using: 'docker'
@@ -435,6 +568,9 @@ runs:
   post-entrypoint: 'cleanup.sh'
 ```
 
+
+
+
 ### `runs.args`
 
 **可选** 定义 Docker 容器输入的字符串数组。 输入可包含硬编码的字符串。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。
@@ -447,9 +583,13 @@ runs:
 
 有关将 `CMD` 指令与 {% data variables.product.prodname_actions %} 一起使用的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)”。
 
+
+
 #### Example: Defining arguments for the Docker container
 
 {% raw %}
+
+
 ```yaml
 runs:
   using: 'docker'
@@ -459,24 +599,37 @@ runs:
     - 'foo'
     - 'bar'
 ```
+
+
 {% endraw %}
 
+
+
 ## `branding`
 
 您可以使用颜色和 [Feather](https://feathericons.com/) 图标创建徽章，以个性化和识别操作。 徽章显示在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中的操作名称旁边。
 
+
+
 ### Example: Configuring branding for an action
 
+
+
 ```yaml
 branding:
   icon: 'award'  
   color: 'green'
 ```
 
+
+
+
 ### `branding.color`
 
 徽章的背景颜色。 可以是以下之一：`white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple` 或 `gray-dark`。
 
+
+
 ### `branding.icon`
 
 要使用的 [Feather](https://feathericons.com/) 图标的名称。 <!-- 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index b1bd8075ff..52cc87e50c 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
 
 You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 1. Click **New self-hosted runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
@@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
 
 You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 1. Click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 
@@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use
 
 New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
 1. Click **Add new**, then click **New runner**.
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
-{% ifversion ghec or ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
 
 {% data reusables.github-actions.self-hosted-runner-public-repo-access %}
-{% endif %}
 
 ### Making enterprise runners available to repositories
 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index dc2789f2cf..3f69732a46 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -46,7 +46,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 
 创建组时，必须选择用于定义哪些仓库有权访问运行器组的策略。
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
@@ -61,12 +61,11 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. 在“Self-hosted runners（自托管运行器）”部分，单击 **Add new（新增）**，然后单击 **New group（新组）**。
+1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**.
 
     ![添加运行器组](/assets/images/help/settings/actions-org-add-runner-group.png)
 1. 输入运行程序组的名称，并分配仓库访问策略。
@@ -95,7 +94,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 
 创建组时，必须选择用于定义哪些组织有权访问运行器组的策略。
 
-{% ifversion ghec %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -113,8 +112,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -144,7 +142,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 ## 更改自托管运行器组的访问策略
 
 您可以更新运行器组的访问策略，或重命名运行器组。
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
 1. 修改访问选项或更改运行器组名称。
@@ -158,8 +156,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
    更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
    {% endwarning %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
 {% endif %}
 
@@ -181,17 +178,18 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 ## 将自托管的运行器移动到组
 
 如果您在注册过程中没有指定运行器组，新的自托管运行器将自动分配到默认组，然后可以移到另一个组。
-{% ifversion ghec or ghes > 3.1 or ghae %}
+
 {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 1. 在“Runners（运行器）”列表中，单击您要配置的运行器。
 2. 选择运行器组下拉菜单。
 3. 在“Move runner to group（将运行器移动到组）”中，选择运行器的目的地组。
-{% endif %}
-{% ifversion ghes < 3.2 or ghae %}
-1. 在设置页面的“Self-hosted runners（自托管运行器）：部分，找到要移动的运行器的当前组，并展开组成员列表。 ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png)
+{% elsif ghae or ghes < 3.4 %}
+1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png)
 2. 选中自托管运行器旁边的复选框，然后单击 **Move to group（移动到组）**以查看可用的目的地。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move.png)
 3. 要移动运行器，请单击目标组。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
+
 ## 删除自托管运行器组
 
 自托管运行器在其组被删除时将自动返回到默认组。
@@ -201,8 +199,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组
 1. 在组列表中，在要删除的组右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。
 2. 要删除组，请单击 **Remove group（删除组）**。
 3. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。
-{% endif %}
-{% ifversion ghes < 3.2 or ghae %}
+{% elsif ghes < 3.2 %}
 1. 在设置页面的“Self-hosted runners（自托管运行器）”部分，找到要删除的组，然后单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 按钮。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
 1. 要删除组，请单击 **Remove group（删除组）**。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-remove.png)
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index dc2fcb9f87..27dcfa5717 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -30,20 +30,20 @@ shortTitle: 删除自托管的运行器
 要从用户仓库删除自托管的运行器，您必须是仓库所有者。 对于组织仓库，您必须是组织所有者或拥有该仓库管理员的权限。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
+
 ## 从组织中删除运行器
 
 {% note %}
@@ -57,19 +57,20 @@ shortTitle: 删除自托管的运行器
 要从组织删除自托管的运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+{% ifversion fpt or ghes > 3.3 or ghec %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions %}
 {% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% else %}
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
+
 ## 从企业中删除运行器
 
 {% ifversion fpt %}
@@ -85,19 +86,17 @@ shortTitle: 删除自托管的运行器
 
 {% endnote %}
 
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+To remove a self-hosted runner from an enterprise, you must be an enterprise owner. 建议您也访问自托管的运行器机器。 For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
-{% ifversion ghec %}
-要从企业帐户删除自托管运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 添加自托管运行器的信息，请参阅[企业管理 GitHub Actions API](/rest/reference/enterprise-admin#github-actions)。
+{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
-{% elsif ghae or ghes %}
-要在
-{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是企业所有者。 建议您也访问自托管的运行器机器。
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 5cdb8720b9..e8637250d7 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -19,13 +19,13 @@ shortTitle: 标签运行器
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
 ## 创建自定义标签
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
  1. 在“Labels（标签）”部分，单击 {% octicon "gear" aria-label="The Gear icon" %}。
  1. 在“Find or create a label（查找或创建标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
@@ -34,35 +34,38 @@ shortTitle: 标签运行器
 
 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
+
 ## 分配标签给自托管的运行器
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.runner-label-settings %}
   1. 要将标签分配给您的自托管运行器，在“Find or create a label（查找或创建标签）”字段中单击标签。
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
 1. 单击标签以将其分配给您的自托管运行器。
 {% endif %}
+
 ## 删除自托管运行器中的自定义标签
-{% ifversion fpt or ghec %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.runner-label-settings %}
   1. 在“Find or create a label（查找或创建标签）”字段中，分配的标签使用
 {% octicon "check" aria-label="The Check icon" %} 图标来标记。 单击标记的标签以将其从您的自托管运行器取消分配。
-{% endif %}
-{% ifversion ghae or ghes %}
+{% elsif ghae or ghes < 3.4 %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
 1. 单击分配的标签以将其从您的自托管运行器中删除。 {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
+
 ## 使用配置脚本创建和分配标签
 
 您可以使用自托管运行器上的配置脚本创建和分配自定义标签。 例如，此命令将名为 `gpu` 的标签分配给自托管运行器。
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index 3157700133..a27d3bf763 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -96,7 +96,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env:
@@ -167,7 +167,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env:
@@ -246,7 +246,7 @@ jobs:
       - name: Validate Gradle wrapper
         uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
       - name: Publish package
-        uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021
+        uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7
         with:
           arguments: publish
         env: {% raw %}
diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
index b3415aed02..5f8c322fbf 100644
--- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
@@ -80,16 +80,17 @@ jobs:
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 下表显示默认情况下授予 `GITHUB_TOKEN` 的权限。 People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
 
-| 作用域      | 默认访问<br>（允许） | 默认访问<br>（限制） | 复刻的仓库的最大访问权限<br> |
-| -------- | ------------------ | ------------------ | ---------------------- |
-| 操作       | 读/写                | 无                  | 读取                     |
-| 检查       | 读/写                | 无                  | 读取                     |
-| 内容       | 读/写                | 读取                 | 读取                     |
-| 部署       | 读/写                | 无                  | 读取                     |
-| id-token | 读/写                | 无                  | 读取                     |
-| 议题       | 读/写                | 无                  | 读取                     |
-| 元数据      | 读取                 | 读取                 | 读取                     |
-| 包        | 读/写                | 无                  | 读取                     |
+| 作用域      | 默认访问<br>（允许） | 默认访问<br>（限制） | 复刻的仓库的最大访问权限<br>            |
+| -------- | ------------------ | ------------------ | --------------------------------- |
+| 操作       | 读/写                | 无                  | 读取                                |
+| 检查       | 读/写                | 无                  | 读取                                |
+| 内容       | 读/写                | 读取                 | 读取                                |
+| 部署       | 读/写                | 无                  | read |{% ifversion fpt or ghec %}
+| id-token | 读/写                | 无                  | read 
+{% endif %}
+| 议题       | 读/写                | 无                  | 读取                                |
+| 元数据      | 读取                 | 读取                 | 读取                                |
+| 包        | 读/写                | 无                  | 读取                                |
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6187 %}
 | pages         | read/write  | none | read |
 {%- endif %}
diff --git a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md
index d8cfa79d92..b029a19ddd 100644
--- a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -202,6 +202,10 @@ The same principles described above for using third-party actions also apply to
 {% data reusables.actions.outside-collaborators-internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."
 {% endif %}
 
+## Using OpenSSF Scorecards to secure workflows
+
+[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions.
+
 ## 受损运行器的潜在影响
 
 这些部分考虑了当攻击者能够对 {% data variables.product.prodname_actions %} 运行器运行恶意命令时可以采取的一些步骤。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 61e750cc30..6afb61b812 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -699,7 +699,7 @@ All Storage tests passed
 
 `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}.
 
-For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/).
+For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/).
 
 ### git-import-detect
 
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 3b86021a4a..0eaf6791cf 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -47,7 +47,7 @@ redirect_from:
 | -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
 | Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
 | Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
-| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | OneLogin                                     | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | PingOne                                      | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | Shibboleth                                   | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index cabcaf41d5..fbfb3ee346 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,7 +18,7 @@ shortTitle: 部署密钥
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
 {% else %}
 3. 在左侧边栏中，单击 **Deploy keys（部署密钥）**。 ![部署密钥设置](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 319efc5029..50e80e1834 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -22,7 +22,7 @@ shortTitle: 安全日志
 安全日志列出了过去 90 天内执行的所有操作。
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else %}
 1. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 ![安全日志选项卡](/assets/images/help/settings/audit-log-tab.png)
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index bdf451e3c6..e6cf3e25a0 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -24,7 +24,7 @@ shortTitle: 更新访问凭据
 1. 要请求新密码，请访问 {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}。
 2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. ![密码重置电子邮件请求对话框](/assets/images/help/settings/password-recovery-email-request.png)
 3. 我们将向您发送一封电子邮件，其中含有可让您重置密码的链接。 您必须在收到电子邮件后的 3 小时内单击此链接。 如果您没有收到来自我们的电子邮件，请确保检查垃圾邮件文件夹。
-4. 如果您启用了双重身份验证，将提示您获得 2FA 凭据。 键入您的 2FA 凭据或 2FA 恢复代码之一，然后单击 **Verify（验证）**。 ![双重身份验证提示](/assets/images/help/2fa/2fa-password-reset.png)
+4. 如果您启用了双重身份验证，将提示您获得 2FA 凭据。 Type your authentication code or one of your recovery codes and click **Verify**. If you have added a security key to your account, you can insert the key and click **Use security key** instead of typing an authentication code. ![双重身份验证提示](/assets/images/help/2fa/2fa-password-reset.png)
 5. 键入新密码，确认新密码，然后单击 **Change password（更改密码）**。 有关创建强密码的帮助，请参阅“[创建强密码](/articles/creating-a-strong-password)”
   {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
   ![密码恢复框](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 4977a6020b..bf6ba3db75 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -64,7 +64,7 @@ If you know your password for {% data variables.product.product_location %} but
 
 {% note %}
 
-**注**：出于安全原因，使用一次性密码验证来重新获得帐户访问权限可能需要 1-3 个工作日。 {% data variables.product.company_short %} will not review additional requests submitted during this time.
+**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time.
 
 {% endnote %}
 
@@ -101,6 +101,6 @@ If you know your password for {% data variables.product.product_location %} but
     - 如果您之前已经设置个人访问令牌，并且想使用个人访问令牌进行验证，请单击 **Personal access token（个人访问令牌）**。
 
    ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png)
-1. {% data variables.contact.github_support %} 的成员将在 1-3 个工作日内审查您的请求并给您发送电子邮件。 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。
+1. A member of {% data variables.contact.github_support %} will review your request and email you within three business days. 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。
 
 {% endif %}
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index e1a1f1aa70..4d398cf069 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -76,7 +76,7 @@ shortTitle: GitHub Actions 的计费
 
 ### 样品分钟数成本计算
 
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
 
 - 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
   - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
index 25412c70df..d27d4e08ce 100644
--- a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
@@ -36,7 +36,7 @@ You can create a default security policy that will display in any of your organi
 {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %}
 ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
 
-{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
 
 1. Click your profile photo, then click **Organizations**.
 2. Click **Settings** next to your organization.
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index 6336b09402..1401e0a134 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -30,11 +30,17 @@ shortTitle: Use Dependabot with Actions
 
 {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
 
-对于 {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) 使用 `pull_request`、`pull_request_review`、`pull_request_review_comment` 和 `push` 事件发起的工作流程，适用以下限制：
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %}
+For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply:
+{% endif %}
 
 - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %}
 - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %}
+For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available.
+{% endif %}
+
 更多信息请参阅“[保持 GitHub Actions 和工作流程安全：阻止 pwn 请求](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)”。
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
@@ -62,13 +68,13 @@ jobs:
 
 {% endraw %}
 
-更多信息请参阅“[修改 GITHUB_TOKEN 的权限](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)”。
+For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)."
 
 ### 访问密钥
 
-When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. 更多信息请参阅“[管理 Dependabot 的加密密码](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)”。
+When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
 
-{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. 更多信息请参阅“[加密密码](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)”。
+{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)."
 
 If you have a workflow that will be triggered by {% data variables.product.prodname_dependabot %} and also by other actors, the simplest solution is to store the token with the permissions required in an action and in a {% data variables.product.prodname_dependabot %} secret with identical names. Then the workflow can include a single call to these secrets. If the secret for {% data variables.product.prodname_dependabot %} has a different name, use conditions to specify the correct secrets for different actors to use. For examples that use conditions, see "[Common automations](#common-dependabot-automations)" below.
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 8b835ed644..9a41ccbd2a 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -58,7 +58,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
 
 You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
index 6d2de3a534..f0e5dc57aa 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md
@@ -46,8 +46,6 @@ There are three reasons why an alert may have no pull request link:
 
 If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert.
 
-![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png)
-
 ## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %}
 
 When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab.
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 2e0ad140d1..4a967cf2fb 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -103,17 +103,17 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the
 {% ifversion fpt or ghec %}
 ## Does each dependency vulnerability generate a separate alert?
 
-When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability.
+When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest.
 
-The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities.
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png)
 
-![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png)
+Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest.
 
-When you click to display the alert details, you can see how many vulnerabilities are included in the alert.
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png)
 
-![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
+The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies.
 
-**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers.
+**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
 {% endif %}
 
 ## Further reading
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index 5cc2ff8d17..4f6be9e0d5 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -25,7 +25,7 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. 您可以选择下拉菜单对警报列表进行排序，并且可以单击特定警报以获取更多详细信息。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
+Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)“。
@@ -37,11 +37,26 @@ Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab l
 ## 关于仓库中有漏洞的依赖项的更新
 
 {% data variables.product.product_name %} 在检测到您的代码库正在使用具有已知漏洞的依赖项时会生成 {% data variables.product.prodname_dependabot_alerts %}。 对于启用了 {% data variables.product.prodname_dependabot_security_updates %} 的仓库，当 {% data variables.product.product_name %} 在默认分支中检测到有漏洞的依赖项时，{% data variables.product.prodname_dependabot %} 会创建拉取请求来修复它。 拉取请求会将依赖项升级到避免漏洞所需的最低安全版本。
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`).
+
+Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %}
 {% endif %}
 
 ## 查看和更新有漏洞的依赖项
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png)
+1. Click the alert that you would like to view. ![在警报列表中选择的警报](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png)
+1. 查看漏洞的详细信息以及包含自动安全更新的拉取请求（如果有）。
+1. （可选）如果还没有针对该警报的 {% data variables.product.prodname_dependabot_security_updates %} 更新，要创建拉取请求以解决该漏洞，请单击 **Create {% data variables.product.prodname_dependabot %} security update（创建 Dependabot 安全更新）**。 ![创建 {% data variables.product.prodname_dependabot %} 安全更新按钮](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
+1. 当您准备好更新依赖项并解决漏洞时，合并拉取请求。 {% data variables.product.prodname_dependabot %} 提出的每个拉取请求都包含可用于控制 {% data variables.product.prodname_dependabot %} 的命令的相关信息。 更多信息请参阅“[管理依赖项更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。
+1. （可选）如果警报正在修复、不正确或位于未使用的代码中，请选择“Dismiss（忽略）”，然后单击忽略警报的原因。 ![选择通过 "Dismiss（忽略）"下拉菜单忽略警报的原因](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png)
+
+{% elsif ghes = 3.3 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -51,7 +66,7 @@ Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab l
 1. 当您准备好更新依赖项并解决漏洞时，合并拉取请求。 {% data variables.product.prodname_dependabot %} 提出的每个拉取请求都包含可用于控制 {% data variables.product.prodname_dependabot %} 的命令的相关信息。 更多信息请参阅“[管理依赖项更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。
 1. （可选）如果警报正在修复、不正确或位于未使用的代码中，请选择“Dismiss（忽略）”，然后单击忽略警报的原因。 ![选择通过 "Dismiss（忽略）"下拉菜单忽略警报的原因](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
-{% elsif ghes > 3.0 or ghae-issue-4864 %}
+{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 9dfc90486b..0956aede41 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -88,7 +88,7 @@ The recommended formats explicitly define which versions are used for all direct
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
 | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
 | Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
-{%- ifversion fpt or ghes > 3.3 %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %}
 | Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
 | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
 | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
index 89bcf4cde1..74c583d24e 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -21,6 +21,8 @@ You can report users that have violated {% data variables.product.prodname_dotco
 
 If reported content is enabled for a public repository, you can also report content directly to repository maintainers.
 
+Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer).
+
 ## Reporting a user
 
 {% data reusables.profile.user_profile_page_navigation %}
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index 1f8746b197..c74337bd71 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -293,10 +293,10 @@ Accept: application/xml
 
 可选的 `redirect_uri` 参数也可用于本地主机 URL。 如果应用程序指定 URL 和端口，授权后，应用程序用户将被重定向到提供的 URL 和端口。 `redirect_uri` 不需要匹配应用程序回调 url 中指定的端口。
 
-对于 `http://localhost/path` 回调 URL，您可以使用此 `redirect_uri`：
+For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`:
 
 ```
-http://localhost:1234/path
+http://127.0.0.1:1234/path
 ```
 
 ## 为 OAuth 应用程序创建多个令牌
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index 5e46b9bea5..605b0a35f5 100644
--- a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -46,10 +46,10 @@ shortTitle: 扩展和集成
 
 ### Slack 与 {% data variables.product.product_name %} 集成
 
-您可以订阅仓库或组织，并获得有关议题、拉取请求、提交、发布、部署审查和部署状态的实时更新。 您还可以执行关闭或打开议题等活动，并在不离开 Slack 的情况下提供丰富的议题和拉取请求参考。
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 您还可以执行关闭或打开议题等活动，并在不离开 Slack 的情况下提供丰富的议题和拉取请求参考。
 
 The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). 更多信息请访问 Marketplace 中的 [Slack 集成应用程序](https://github.com/marketplace/slack-github)。
 
 ### Microsoft Teams 与 {% data variables.product.product_name %} 集成
 
-您可以订阅仓库或组织，并获得有关议题、拉取请求、提交、部署审查和部署状态的实时更新。 您也可以执行一些活动，如关闭或打开议题、评论您的议题和拉取请求，以及提供丰富的议题和拉取请求引用而不离开 Microsoft Teams。 更多信息请访问 Microsoft AppSource 中的 [Microsoft Teams 集成应用程序](https://appsource.microsoft.com/en-us/product/office/WA200002077)。
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 您也可以执行一些活动，如关闭或打开议题、评论您的议题和拉取请求，以及提供丰富的议题和拉取请求引用而不离开 Microsoft Teams。 更多信息请访问 Microsoft AppSource 中的 [Microsoft Teams 集成应用程序](https://appsource.microsoft.com/en-us/product/office/WA200002077)。
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 3da91c787d..d3496d0140 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -195,6 +195,8 @@ $ git remote -v
 `git remote rm` 命令使用一个参数：
 * 远程名称，例如 `destination`
 
+Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.
+
 ## 示例
 
 以下示例假设您[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，即推荐使用的方法。
@@ -217,7 +219,7 @@ $ git remote -v
 
 {% warning %}
 
-**注**：`git remote rm` 不会从服务器中删除远程仓库。  它只是从本地仓库中删除远程及其引用。
+**Note**: `git remote rm` does not delete the remote repository from the server.  它只是从本地仓库中删除远程及其引用。
 
 {% endwarning %}
 
diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
index c8b27e59df..0231b06a5a 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -36,10 +36,31 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th
 - **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
 {% endif %}
 
+{% ifversion fpt or ghec %}
+The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories.
+
+{% ifversion fpt %}
+|                   | Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} |
+| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: |
+| Code scanning     | Yes                         | No                                           | Yes                                        |
+| Secret scanning   | Yes **(limited functionality only)** | No                                           | Yes                                       |
+| Dependency review | Yes                         | No                                           | Yes                                       |
+{% endif %}
+{% ifversion ghec %}
+|                   | Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} |
+| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: |
+| Code scanning     | Yes                         | No                                           | Yes                                        |
+| Secret scanning   | Yes **(limited functionality only)** | No                                           | Yes                                       |
+| Dependency review | Yes                         | No                                           | Yes                                       |
+| Security overview | No                          | No                                           | Yes                                          |
+{% endif %}
+
+{% endif %}
+
 For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
 {% ifversion fpt or ghec %}
-{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
 {% endif %}
 
 {% ifversion ghes or ghec %}
@@ -59,9 +80,9 @@ The site administrator must enable {% data variables.product.prodname_advanced_s
 Once your system is set up, you can enable and disable these features at the organization or repository level.
 
 {%- elsif ghec %}
-For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. 
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
 
-For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. 
+For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level.
 
 {%- elsif ghae %}
 You can enable and disable these features at the organization or repository level.
diff --git a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md
index 93671db3a5..604c3edecb 100644
--- a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md
+++ b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md
@@ -22,7 +22,7 @@ GitHub 社区的主要目的是协作处理软件项目。 我们希望人们能
 
 * **包容开放** - 其他协作的经验水平或背景可能与您不同，但这并不意味着他们不能贡献好的想法。 鼓励大家欢迎新的协作者和刚入门的新手。
 
-* **互相尊重。**粗鲁是正常对话的天敌。 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。
+* **Respect each other** - Nothing sabotages healthy conversation like rudeness. 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。
 
   您可能要发表反对的意见。 没问题。 但请记住，您的批评要对事不对人。 不要说脏话、人身攻击、纠结于帖子的语气而罔顾其实际内容或制造下意识的矛盾。 而应该提供合理的反驳论据，保持友善的对话。
 
diff --git a/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md b/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md
index 4f02a715f8..921bbd2c20 100644
--- a/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md
+++ b/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md
@@ -23,3 +23,5 @@ GitHub 商标政策可用于报告涉嫌使用您公司或企业的名称、徽
 
 ## [GitHub 私人信息删除政策](/github/site-policy/github-private-information-removal-policy)
 GitHub 私人信息删除政策可用于报告私人（机密并且会造成安全风险）的数据，但这些数据不一定受版权或商标保护。
+
+Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer).
diff --git a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md
index e9ebc3409d..2972924536 100644
--- a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md
+++ b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md
@@ -12,7 +12,7 @@ topics:
 
 ## 概览
 
-下面是一些帮助您启动和运行 GraphQL API v4 的快速链接：
+Here are some quick links to get you up and running with the GraphQL API:
 
 * [身份验证](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)
 * [根端点](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint)
@@ -36,9 +36,9 @@ topics:
 
 ## GitHub 为什么使用 GraphQL
 
-GitHub 选择将 GraphQL 用于 API v4，因为它可以为我们的集成商提供明显更高的灵活性。 准确定义所需数据&mdash;_仅仅_是您所需的数据&mdash;的能力是它超越 REST API v3 端点的强大优势。 GraphQL 可用于将多个 REST 请求替换为_单个调用_，以获取您指定的数据。
+GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want&mdash;and _only_ the data you want&mdash;is a powerful advantage over traditional REST API endpoints. GraphQL 可用于将多个 REST 请求替换为_单个调用_，以获取您指定的数据。
 
-有关 GitHub 为什么移动到 GraphQL 的详细信息，请参阅原始[公告博客文章](https://githubengineering.com/the-github-graphql-api/)。
+For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/).
 
 ## 关于 GraphQL 架构引用
 
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
index bc1b0317b2..3a30602e9f 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -19,9 +19,9 @@ shortTitle: 审核已安装的集成
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
-{% elsif ghae or ghes < 3.4 %}
+{% else %}
 1. 在左侧边栏中，单击 **Installed {% data variables.product.prodname_github_apps %}s（安装的 GitHub 应用程序）**。 ![组织设置边栏中安装的 {% data variables.product.prodname_github_apps %}选项卡](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 {% endif %}
 2. 在您要审查的 {% data variables.product.prodname_github_app %} 旁边，单击 **Configure（配置）**。 ![配置按钮](/assets/images/help/organizations/configure-installed-integration-button.png)
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index cbffbca64c..02d3b700b3 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -40,7 +40,7 @@ Before you can add someone as an outside collaborator on a repository, the perso
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 ![搜索字段以键入要邀请加入仓库的人员姓名](/assets/images/help/repository/manage-access-invite-search-field.png)
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 9c96b97417..e5c3c0753d 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -28,9 +28,9 @@ permissions: People with admin access to a repository can manage access to the r
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.repositories.click-collaborators-teams %}
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
 {% data reusables.organizations.invite-teams-or-people %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index 1e714b59e6..8c9dfb369a 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -24,7 +24,7 @@ shortTitle: 禁用项目板
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
 {% endif %}
 1. 决定是否禁用组织范围的项目板，禁用组织中的仓库项目板，或两者均禁用。 然后，在“项目”（项目）下：
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
index 34feae56fb..94e8b3c7ba 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -10,12 +10,12 @@ versions:
 shortTitle: 集成 Jira
 ---
 
-{% ifversion ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion ghes > 3.4 or ghae-issue-5658 %}
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png)
 1. 单击 **New OAuth App（新建 OAuth 应用程序）**。
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 {% data reusables.user_settings.access_settings %}
 1. 在左侧边栏的 **Organization settings（组织设置）**下，单击组织的名称。 ![侧边栏组织名称](/assets/images/help/settings/organization-settings-from-sidebar.png)
 1. 在左侧边栏的 **Developer settings（开发者设置）**下，单击 **OAuth applications（OAuth 应用程序）**。 ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index fe929d9881..3d1225948b 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -15,26 +15,37 @@ topics:
 shortTitle: 限制仓库创建
 ---
 
-您可以选择成员是否可以在组织中创建仓库。 If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
+您可以选择成员是否可以在组织中创建仓库。 {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository.
+
+{% ifversion fpt %}
+Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization).
+{% endif %}
 
-组织所有者始终可以创建任何类型的仓库。
 {% ifversion ghec or ghae or ghes %}
-{% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
+Enterprise owners can restrict the options you have available for your organization's repository creation policy. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。
+{% endif %}
 
 {% warning %}
 
-**警告**：此设置仅限制在仓库创建时可用的可见性选项，而不会限制以后更改仓库可见性的能力。 For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+**警告**：此设置仅限制在仓库创建时可用的可见性选项，而不会限制以后更改仓库可见性的能力。 有关限制更改现有仓库可见性的更多信息，请参阅“[限制组织的仓库可见性更改](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)”。
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
-5. Under "Repository creation", select one or more options.
+5. 在“Repository creation（仓库创建）”下，选择一个或多个选项。
 
    {%- ifversion ghes or ghec or ghae %}
    ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
    ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+
+   {% note %}
+
+   **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.
+
+   {% endnote %}
    {%- endif %}
+
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index a9d17a0738..4c1f6a07f8 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -57,7 +57,7 @@ When code owners are automatically requested for review, the team is still remov
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
@@ -71,7 +71,7 @@ When code owners are automatically requested for review, the team is still remov
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
 {% else %}
 1. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index e882b1f808..a15a7a7cdd 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -22,7 +22,7 @@ topics:
 
 **注：**在处理拉取请求时，请记住：
 * 如果操作的是[共享仓库型号](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)，建议对拉取请求使用主题分支。 从任何分支或提交都可发送拉取请求，但如果需要更新提议的更改，则可使用主题分支推送跟进提交。
-* 在推送提交到拉取请求时，请勿强制推送。 Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
+* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index ef6028cd86..cc39fced48 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -17,7 +17,7 @@ topics:
 
 复刻仓库类似于复制仓库，主要有两点差异：
 
-* 您可以使用拉取请求将更改从用户拥有的复刻提交到原始仓库，也称为*上游*仓库。
+* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository.
 * 您可以通过同步复刻与上游仓库，将更改从上游仓库提交到本地复刻。
 
 {% data reusables.repositories.you-can-fork %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
index f887726845..902959798e 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -22,7 +22,7 @@ Anyone with admin permissions to a repository can configure autolink references
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
 {% else %}
 1. 在左侧边栏中，单击 **Autolink references（自动链接引用）**。 ![左侧边栏中的自动链接引用选项卡](/assets/images/help/repository/autolink-references-tab.png)
diff --git a/translations/zh-CN/content/rest/reference/billing.md b/translations/zh-CN/content/rest/reference/billing.md
index 7d26c46737..e645927dbc 100644
--- a/translations/zh-CN/content/rest/reference/billing.md
+++ b/translations/zh-CN/content/rest/reference/billing.md
@@ -4,6 +4,7 @@ intro: 'With the Billing API, you can monitor the charges and usage {% data vari
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '>=3.4'
 topics:
   - API
 miniTocMaxHeadingLevel: 3
diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md
index 006d78ee79..230e3f76b5 100644
--- a/translations/zh-CN/content/rest/reference/enterprise-admin.md
+++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md
@@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer
 
 {% endif %}
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes > 3.3 %}
 ## Billing
 
 {% for operation in currentRestOperations %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index 7111b2d945..7693927a99 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else  %}
 1. 在 Setting（设置）边栏中，单击 **Audit log（审核日志）**。 ![边栏中的组织审核日志设置](/assets/images/help/organizations/org-settings-audit-log.png)
diff --git a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index 1a327d39fa..c52188f4f4 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 3. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else  %}
 3. 在左侧边栏中，单击 **Audit log（审核日志）**。 ![审核日志选项卡](/assets/images/enterprise/site-admin-settings/audit-log-tab.png)
diff --git a/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md b/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md
index 52c7d535ab..1aed5cdf6b 100644
--- a/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md
+++ b/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
-{% elsif ghes > 3.2%}
+{% else %}
 1. 在侧边栏中，单击 **{% data variables.product.prodname_dependabot %}**。 ![{% data variables.product.prodname_dependabot %} 密钥边栏选项](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md b/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
index 4336f18187..0620d64524 100644
--- a/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
@@ -5,8 +5,8 @@ permissions:
   actions: read|write|none
   checks: read|write|none
   contents: read|write|none
-  deployments: read|write|none
-  id-token: read|write|none
+  deployments: read|write|none{% ifversion fpt or ghec %}
+  id-token: read|write|none{% endif %}
   issues: read|write|none
   discussions: read|write|none
   packages: read|write|none
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
index 5f69552bc6..471c62ea06 100644
--- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
+++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
@@ -12,6 +12,6 @@
      2. 在左边栏中，单击 **Enterprise overview（企业概览）**。
      3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
 2. Navigate to the "Runner groups" settings:
-   * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %}
-   * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghec %}, then click the **Runners groups** tab{% endif %}.{% endif %}
+   * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %}
+   * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %}
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md b/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
index 4eabba8e7e..7557c2ad5a 100644
--- a/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
+++ b/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左侧边栏中，单击 **Secrets（密码）**。
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/billing_plans.md b/translations/zh-CN/data/reusables/organizations/billing_plans.md
index ed5792ba3e..2980a65c03 100644
--- a/translations/zh-CN/data/reusables/organizations/billing_plans.md
+++ b/translations/zh-CN/data/reusables/organizations/billing_plans.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在组织的 Settings（设置）侧边栏中，单击 **Billing & plans（帐单和计划）**。 ![帐单设置](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md
index a606fbb1fe..a42349f5ed 100644
--- a/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md
+++ b/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左侧边栏中，单击 **{% data variables.product.prodname_github_apps %}**。 ![{% data variables.product.prodname_github_apps %} 设置](/assets/images/help/organizations/github-apps-settings-sidebar.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/member-privileges.md b/translations/zh-CN/data/reusables/organizations/member-privileges.md
index e2427fc02c..304c706a7e 100644
--- a/translations/zh-CN/data/reusables/organizations/member-privileges.md
+++ b/translations/zh-CN/data/reusables/organizations/member-privileges.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
-{% elsif ghae or ghes < 3.4 %}
+{% else %}
 4. 在左侧边栏中，单击 **Member privileges（成员权限）**。 ![组织设置中的成员权限选项](/assets/images/help/organizations/org-settings-member-privileges.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/repository-defaults.md b/translations/zh-CN/data/reusables/organizations/repository-defaults.md
index 9d30bab3cc..31d188fa73 100644
--- a/translations/zh-CN/data/reusables/organizations/repository-defaults.md
+++ b/translations/zh-CN/data/reusables/organizations/repository-defaults.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左边栏中，单击 **Repository defaults（仓库默认值）**。 ![仓库默认值选项卡](/assets/images/help/organizations/repo-defaults-tab.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/security-and-analysis.md b/translations/zh-CN/data/reusables/organizations/security-and-analysis.md
index 37774fc461..b54d899179 100644
--- a/translations/zh-CN/data/reusables/organizations/security-and-analysis.md
+++ b/translations/zh-CN/data/reusables/organizations/security-and-analysis.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![组织设置中的"Security & analysis（安全和分析）"选项卡](/assets/images/help/organizations/org-settings-security-and-analysis.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/security.md b/translations/zh-CN/data/reusables/organizations/security.md
index 9a20cf5fe7..f44d33cd5a 100644
--- a/translations/zh-CN/data/reusables/organizations/security.md
+++ b/translations/zh-CN/data/reusables/organizations/security.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
 {% else  %}
 1. 在左边栏中，单击 **Organization security（组织安全）**。
diff --git a/translations/zh-CN/data/reusables/organizations/teams_sidebar.md b/translations/zh-CN/data/reusables/organizations/teams_sidebar.md
index 8725b2c756..d3a0aa94ee 100644
--- a/translations/zh-CN/data/reusables/organizations/teams_sidebar.md
+++ b/translations/zh-CN/data/reusables/organizations/teams_sidebar.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
 {% else %}
 1. 在 Settings（设置）侧边栏中，单击 **Teams（团队）**。 ![组织设置侧边栏中的团队选项卡](/assets/images/help/settings/settings-sidebar-team-settings.png)
diff --git a/translations/zh-CN/data/reusables/organizations/verified-domains.md b/translations/zh-CN/data/reusables/organizations/verified-domains.md
index 2c428cfd09..bcd9a7872b 100644
--- a/translations/zh-CN/data/reusables/organizations/verified-domains.md
+++ b/translations/zh-CN/data/reusables/organizations/verified-domains.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左侧边栏中，单击 **Verified & approved domains（已验证并批准的域名）**。 ![“已验证并批准的域名”选项卡](/assets/images/help/organizations/verified-domains-button.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/pages/sidebar-pages.md b/translations/zh-CN/data/reusables/pages/sidebar-pages.md
index 39aac8496d..9ceaa0a913 100644
--- a/translations/zh-CN/data/reusables/pages/sidebar-pages.md
+++ b/translations/zh-CN/data/reusables/pages/sidebar-pages.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %}
+{% ifversion fpt or ghes > 3.4 or ghec or ghae-issue-5658 %}
 1. In the "Code & operations" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% else %}
 1. 在左侧边栏中，单击 **Pages（页面）**。 ![左侧边栏中的页面选项卡](/assets/images/help/pages/pages-tab.png)
diff --git a/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
index 5db73f5e10..0afeb7673c 100644
--- a/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
+++ b/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![仓库设置中的"Security & analysis（安全和分析）"选项卡](/assets/images/help/repository/security-and-analysis-tab.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/repository-branches.md b/translations/zh-CN/data/reusables/repositories/repository-branches.md
index 679e2d97d8..e32f6b4e31 100644
--- a/translations/zh-CN/data/reusables/repositories/repository-branches.md
+++ b/translations/zh-CN/data/reusables/repositories/repository-branches.md
@@ -1,5 +1,5 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
-{% elsif ghes < 3.4 or ghae %}
+{% else %}
 1. 在左侧菜单中，单击 **Branches（分支）**。 ![仓库选项子菜单](/assets/images/help/repository/repository-options-branch.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md b/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md
index a5de73765d..a14fb131d9 100644
--- a/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
 {% else %}
 1. 单击 **Notifications（通知）**。 ![侧边栏中的通知按钮](/assets/images/help/settings/notifications_menu.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/access_applications.md b/translations/zh-CN/data/reusables/user_settings/access_applications.md
index 1c307bc2a7..eeff0867bd 100644
--- a/translations/zh-CN/data/reusables/user_settings/access_applications.md
+++ b/translations/zh-CN/data/reusables/user_settings/access_applications.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
 {% else %}
 1. 在左侧边栏中，单击 **Applications**。 ![应用程序选项卡](/assets/images/help/settings/settings-applications.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/account_settings.md b/translations/zh-CN/data/reusables/user_settings/account_settings.md
index e3cd5d53e4..1272ab7619 100644
--- a/translations/zh-CN/data/reusables/user_settings/account_settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/account_settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-next %}
 1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
 {% else %}
 1. 在左侧边栏中，单击 **Account（帐户）**。 ![帐户设置菜单选项](/assets/images/help/settings/settings-sidebar-account-settings.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/appearance-settings.md b/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
index fdd66ad0d7..b27185f75a 100644
--- a/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 {% else %}
 1. 在用户设置侧边栏中，单击 **Appearance（外观）**。
diff --git a/translations/zh-CN/data/reusables/user_settings/developer_settings.md b/translations/zh-CN/data/reusables/user_settings/developer_settings.md
index bd27b9e487..acf04e6323 100644
--- a/translations/zh-CN/data/reusables/user_settings/developer_settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/developer_settings.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
 {% else %}
 1. 在左侧边栏中，单击 **Developer settings**。 ![开发者设置](/assets/images/help/settings/developer-settings.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/emails.md b/translations/zh-CN/data/reusables/user_settings/emails.md
index 872d53bdea..3d87b98068 100644
--- a/translations/zh-CN/data/reusables/user_settings/emails.md
+++ b/translations/zh-CN/data/reusables/user_settings/emails.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
 {% else %}
 1. 在左侧边栏中，单击 **Emails（电子邮件）**。 ![电子邮件选项卡](/assets/images/help/settings/settings-sidebar-emails.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/organizations.md b/translations/zh-CN/data/reusables/user_settings/organizations.md
index d593508a58..5f8c0a6b4e 100644
--- a/translations/zh-CN/data/reusables/user_settings/organizations.md
+++ b/translations/zh-CN/data/reusables/user_settings/organizations.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% else %}
 1. 在用户设置侧边栏中，单击 **Organizations（组织）**。 ![组织的用户设置](/assets/images/help/settings/settings-user-orgs.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/repo-tab.md b/translations/zh-CN/data/reusables/user_settings/repo-tab.md
index 84701bb7be..1d2472de6a 100644
--- a/translations/zh-CN/data/reusables/user_settings/repo-tab.md
+++ b/translations/zh-CN/data/reusables/user_settings/repo-tab.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
 {% else %}
 1. 在左侧边栏中，单击 **Repositories（仓库）**。 ![仓库选项卡](/assets/images/help/settings/repos-tab.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/saved_replies.md b/translations/zh-CN/data/reusables/user_settings/saved_replies.md
index 45ece51af1..aab77e6046 100644
--- a/translations/zh-CN/data/reusables/user_settings/saved_replies.md
+++ b/translations/zh-CN/data/reusables/user_settings/saved_replies.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
 {% else %}
 1. 在左侧边栏中，单击 **Saved replies（已保存回复）**。 ![已保存回复选项卡](/assets/images/help/settings/saved-replies-tab.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/security-analysis.md b/translations/zh-CN/data/reusables/user_settings/security-analysis.md
index 6fb9cc957f..f2c2a73773 100644
--- a/translations/zh-CN/data/reusables/user_settings/security-analysis.md
+++ b/translations/zh-CN/data/reusables/user_settings/security-analysis.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
 {% else %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![安全和分析设置](/assets/images/help/settings/settings-sidebar-security-analysis.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/security.md b/translations/zh-CN/data/reusables/user_settings/security.md
index 8998e91180..2627493a70 100644
--- a/translations/zh-CN/data/reusables/user_settings/security.md
+++ b/translations/zh-CN/data/reusables/user_settings/security.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
 {% else %}
 1. 在左侧边栏中，单击 **Account security（帐户安全）**。 ![用户帐户安全设置](/assets/images/help/settings/settings-sidebar-account-security.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/ssh.md b/translations/zh-CN/data/reusables/user_settings/ssh.md
index 35ecc516f5..3e031b70be 100644
--- a/translations/zh-CN/data/reusables/user_settings/ssh.md
+++ b/translations/zh-CN/data/reusables/user_settings/ssh.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
 {% else %}
 1. 在用户设置侧边栏中，单击 **SSH and GPG keys（SSH 和 GPG 密钥）**。 ![身份验证密钥](/assets/images/help/settings/settings-sidebar-ssh-keys.png)